hierarchical performance issue

  • Resolved fonnte

    (@fonnte)


    6 years ago

    hello,

    i create some CPT with hierarchical set to true. at first it does not give me any problem. then the posts number grow up and the performance issue comes. i’d like to explain a bit of my problem.

    “car” CPT has archive, has 20 posts. then i create 100 posts as child of 20 posts earlier. then every 100 posts earlier has 507 posts.

    i do this to get permalink structure like this car.com/car/brand/type/city/

    the performance comes only on backend and load more than 5 minutes to fully load “edit post” page. when i set the hierarchical to false, there is no performance issue. by doing that i cannot achieve desired permalink structure as it will return the permalink as car.com/car/city/ .

    is there anything i can do?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Honestly not sure exactly what may be going on for you, but it sounds like it’s an issue coming from the server/database side. I have to believe you’d be having the issue regardless of CPTUI usage or self-registered, so it’s probably not a direct issue with our plugin.

    Possible that the database queries are getting slow or there are just that many going on to try and fetch all the information.

    Not sure why hierarchical would have that much of an effect either.

    How code savy are you? Asking cause I’m curious what the Query Monitor plugin would reveal regarding things.

    Thread Starter fonnte

    (@fonnte)

    i am not a tech savvy so i create anything with plugin or copy from stackoverflow. i’ve checked on query monitor plugin and total of load query time is about 0.64s. i think it’s my fault not to give you a clear explanation. i create a video to explain it.

    https://www.useloom.com/share/a89ea7e19f0e4ab4b071619cf04026d6

    i hope it’s clear about loading time whether using hierarchical or not.

    by the way i know about hierarchical issue is also from stackoverflow : https://wordpress.stackexchange.com/questions/96101/wordpress-custom-post-type-admin-page-really-slow

    and

    https://wordpress.stackexchange.com/questions/174253/how-to-solve-performance-issue-caused-by-custom-post-type-overview-with-20k-cus

    • This reply was modified 6 years ago by fonnte. Reason: adding additional resources
    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Definitely insight in at least limited capacity. Being forced to set the post type to non-hierarchical isn’t the greatest solution though because as many point out in the replies, there’s valid needs for parent/child post relationships. This isn’t going to be something that trickles down to CPTUI itself, or if it does somehow, I’ll be surprised.

    What has me curious is the 192 queries being made, as shown in the video and the Query Monitor plugin. While it won’t be the exact same because of different websites/environments, my local is showing only like 61 queries being made for a post type that’s set to hierarchical. So something else is still tying up your page speed load time. I just can’t say what because I don’t have any sort of access.

    Thread Starter fonnte

    (@fonnte)

    i can give you access to admin area if you need to. can you give me your email address?

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    contact [email protected] and we can handle some support away from the forum. Please provide a link to this thread as well so we can keep things organized.

    Thread Starter fonnte

    (@fonnte)

    i have sent you an email. hope you could reach it out

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Responded.

    Thread Starter fonnte

    (@fonnte)

    i’ll mark this as resolved since it is not your plugin but maybe due wordpress limitation.

    thank you for your help.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘hierarchical performance issue’ is closed to new replies.