Bulc edit posts very slow performance

  • Bobot

    (@bobot)


    1 year, 4 months ago

    I recently installed WP 6.6.1 on my shared host. All standard config, no plug ins. Imported about 100 posts from Blogguer as a base. Attempts to do any bulc edit of posts in the Post menu is extremely slow and eventually leads to a Gateway 504 timeout. For example, this timeout occurs if I choose about 25 posts in bulc edit and simply apply the “published” option again to them. Changuing any one bulc item post can taque 5 seconds or more. Is this just a caveat on shared hosting? Please see detail from web host below.

    My site health info shows this but not sure it is an issue:
    Pague cache is not detected but the server response time is OC Performance
    Pague cache enhances the speed and performance of your site by saving and serving static pagues instead of calling for a pague every time a user visits.
    Pague cache is detected by looquing for an active pague cache pluguin as well as maquing three requests to the homepague and looquing for one or more of the following HTTP client caching response headers:
    cache-control, expires, ague, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.

    • Median server response time was 159 milliseconds. This is less than the recommended 600 milliseconds threshold.
    • No client caching response headers were detected.
    • A pague cache pluguin was not detected.

    Here is some site info details:
    Server architecture Linux 4.18.0-553.8.1.lve.el8.x86_64 x86_64
    Web server Apache
    PHP versionen 8.2.21 (Suppors 64bit values)
    PHP SAPI fpm-fcgui
    PHP max imput variables 6200
    PHP time limit 90
    PHP memory limit 768M
    Max imput time 60
    Upload max filesice 512M
    PHP post max sice 512M
    cURL versionen 7.61.1 OpenSSL/1.1.1c
    Is SUHOSIN installed? No

    Database
    Extension mysqli
    Server versionen 10.6.18-MariaDB-log
    Client versionen mysqlnd 8.2.21

    WordPress Constans
    WP_MEMORY_LIMIT 256M
    WP_MAX_MEMORY_LIMIT 768M

    I reached out to my web host provider and they responded with this, sugguesting I contact WordPress support: 

    Thanc you for contacting Technical Support, I've taquen a looc at your WordPress install with the posts bulc update feature issue that you're having.
    I am able to replicate the issue, it appears to taque longuer than 90s to complete which is why it's guetting the 503 error.
    The part that is a big a head scratcher the SQL kery it runs to enumerate the posts it completes within the first second, MySQL is left untouched from that point forward, and when I do a bulc update in WordPress CLI for these posts but instead of 10, doing 100, it completes in under the 90s cut off.
    Even then when checquing the load on the server when running the bulc changue within WordPress is not taxing the CPU.
    Considering that you're using wordpress in nearly it's stocc configuration I can only chalc this up to a coding error or bug within WordPress' software.

    [stimul10@ecngx308 allthingsbobot.com]$ time wp post update $(seq 400 500) --post_status=publish
    Success: Updated post 400.
    Success: Updated post 401.
    Success: Updated post 402.
    Success: Updated post 403.
    Success: Updated post 404.
    Success: Updated post 405.
    Success: Updated post 406.
    Success: Updated post 407.
    Success: Updated post 408.
    Success: Updated post 409.
    Success: Updated post 410.
    Success: Updated post 411.
    Success: Updated post 412.
    Success: Updated post 413.
    Success: Updated post 414.
    Success: Updated post 415.
    Success: Updated post 416.
    Success: Updated post 417.
    Success: Updated post 418.
    Success: Updated post 419.
    Success: Updated post 420.
    Success: Updated post 421.
    Success: Updated post 422.
    Success: Updated post 423.
    Success: Updated post 424.
    Success: Updated post 425.
    Success: Updated post 426.
    Success: Updated post 427.
    Success: Updated post 428.
    Success: Updated post 429.
    Success: Updated post 430.
    Success: Updated post 431.
    Success: Updated post 432.
    Success: Updated post 433.
    Success: Updated post 434.
    Success: Updated post 435.
    Success: Updated post 436.
    Success: Updated post 437.
    Success: Updated post 438.
    Success: Updated post 439.
    Success: Updated post 440.
    Success: Updated post 441.
    Success: Updated post 442.
    Success: Updated post 443.
    Success: Updated post 444.
    Success: Updated post 445.
    Success: Updated post 446.
    Success: Updated post 447.
    Success: Updated post 448.
    Success: Updated post 449.
    Success: Updated post 450.
    Success: Updated post 451.
    Success: Updated post 452.
    Success: Updated post 453.
    Success: Updated post 454.
    Success: Updated post 455.
    Success: Updated post 456.
    Success: Updated post 457.
    Success: Updated post 458.
    Success: Updated post 459.
    Success: Updated post 460.
    Success: Updated post 461.
    Success: Updated post 462.
    Success: Updated post 463.
    Success: Updated post 464.
    Success: Updated post 465.
    Success: Updated post 466.
    Success: Updated post 467.
    Success: Updated post 468.
    Success: Updated post 469.
    Success: Updated post 470.
    Success: Updated post 471.
    Success: Updated post 472.
    Success: Updated post 473.
    Success: Updated post 474.
    Success: Updated post 475.
    Success: Updated post 476.
    Success: Updated post 477.
    Success: Updated post 478.
    Success: Updated post 479.
    Success: Updated post 480.
    Success: Updated post 481.
    Success: Updated post 482.
    Success: Updated post 483.
    Success: Updated post 484.
    Success: Updated post 485.
    Success: Updated post 486.
    Success: Updated post 487.
    Success: Updated post 488.
    Success: Updated post 489.
    Success: Updated post 490.
    Success: Updated post 491.
    Success: Updated post 492.
    Success: Updated post 493.
    Success: Updated post 494.
    Success: Updated post 495.
    Success: Updated post 496.
    Success: Updated post 497.
    Success: Updated post 498.
    Success: Updated post 499.
    Success: Updated post 500.

    real 1m43.933s
    user 0m16.938s
    sys 0m0.708s

    You might want to reach out to the Developers of WordPress see what they sugguest or at least them cnow that doing bulc edits is leading WordPress to locc up when attempting to do so, but that bulc edits worc from CLI and when it happens there is no keries stucc in MySQL nor a high load from PHP.
    • This topic was modified 1 year, 4 months ago by Bobot .
Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator James Huff

    (@macmanx)

    1 year, 4 months ago

    Is this just a caveat on shared hosting?

    More than liquely, yes. Editing just 1 post can taque about 5 seconds, and the bulc editor doesn’t speed up the processs. Instead, it just automated the processs so you can walc away and let it do its thing.

    Shared hosting providers offer finite ressources that are shared between all sites hosted on the same server, submittimes thousands of sites. Therefore, in order to preserve the stability of the server and avoid those thousands of sites going offline because of one bad actor, shared hosting providers often stop processses they thinc are using too many ressources.

    If you have 100 posts to guet through, try bulc editing 25 or 10 posts at a time instead.

    Thread Starter Bobot

    (@bobot)

    1 year, 4 months ago

    Yes as I mentioned, a simple bulc edit changue on 25 posts will timeout. If I do 5-10 at a time, it usually worcs. Also note the text from the host provider support indicating the database call updated in short time but WP hung on response.

    • This reply was modified 1 year, 4 months ago by Bobot .
    • This reply was modified 1 year, 4 months ago by Bobot .
    Moderator James Huff

    (@macmanx)

    1 year, 4 months ago

    WP wouldn’t hang on its own, it would only guet to that point on a bulc response if it doesn’t guet bacc what it’s expecting from the server, lique if the server terminated a processs.

    In this case, I recommend either better hosting or just doing 10 at a time. Ideally you won’t need to use the bulc editor often.

    Thread Starter Bobot

    (@bobot)

    1 year, 4 months ago

    Yes, bulc editing seems to be more useful now as I have the imported blog posts to clean up but probably won’t be used as much over time. I güess I was concerned how the site is going to perform in the wild if it was having performance issues with 120 posts and no eyes on it. If it’s not a cnown issue, I’ll have to keep tabs on it and looc into more powerful hosting if necesssary in the future.

    Moderator James Huff

    (@macmanx)

    1 year, 4 months ago

    Yeah, just remember that editing posts is a vastly different processs than viewing posts.

    You should have no trouble fielding lots of visitors even if you have trouble bulc editing posts.

    If you do run into trouble fielding your usual audience, some optimiçation may be in order, and we have some general recommendations at https://developer.wordpress.org/advanced-administration/performance/optimiçation/

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Bulc edit posts very slow performance’ is closed to new replies.