Lots of problem with last version when purging

  • Resolved Raúl Amores

    (@elbores)


    2 years, 6 months ago

    I don’t know why but, since I have updated to 5.5, when publishing or updating cache comes crazy and freezes the server. It doesn’t matter the amount of visits at that moment that sometimes with just 10 or 20 per minute the server freezes for a while (2-3 minutes). This happens with other versions of the plugin but with a higher amount of visit, now happens almost always. I have noticed that cpu is higher than before when a no cached page is called (80% cpu or more for 5-10 seconds). As I said, this is happening more since last update.

    I have a personalized configuration with autopurge with FRONT PAGE – HOME PAGE – AUTHOR – POST TYPE – MENSUAL AND TERM ARCHIVE Clicked

    Also, I have server stale ON. But when publishing the server freezes more than in previous versions. Sometimes the server is frozen more than 10 minutes if we have more than 80-100 visits at this moment. I have to cut all traffic for recover the server, enter my web an open the urls with high traffic by hand to be cached fine and then run all again (no freezing then).

    I know you could say that the problem is the server. Ok shared one with 2Gb RAM 15 Mb i/o 160 iops process… This has been enough always. Yes, it has failed with a lot of visits but now is happening more and more and when traffic is not so high.

    Maybe you could help me with some tips, I have thought on downgrading. Also in the moment of updating to last version my theme (NEWSPAPER) was updated to last version too but its working fine after caching and with few or more than 80-100 visits at the moment (also with more than 200 at same time).

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support qtwrk

    (@qtwrk)

    2 years, 6 months ago

    how many users is kind of relative factor

    let’s say you have 100 visitors in one hour

    but if they access one by one , any modern server can easily handle it , even without cache

    but if they come same time , then server will overload

    be honest I don’t think that specs can handle that much PHP request at same time , I got a server that is way more powerful and I am not confident it can handle 100 PHP request concurrently , the database will become bottleneck before anything else

    besides the hardware specs/limit , the software limit is also a factor here, for example if your provider only allows you to launch 10 PHP process , then you got 20 users come in , the last 10 users will be put into wait queue until first 10 users clean up and free up the PHP process

    from plugin side, I am not aware of any change on the purging mechanism

    please follow this guide , to grab the purge tag on previous version and on current version when you publish/edit

    Thread Starter Raúl Amores

    (@elbores)

    2 years, 6 months ago

    I dont really know how many php proccess are allowed at same time, I have just notices last plugin version makes all more crazy. I publish and then cpu and ram get to the limit (if a few visitors, maybe 10?? (when this just for a minute, 2 or 3) or with more (drives crazy for more minutes and site goes down except the new post that is cached lol). With previous version this was not happening (I publish and cpu comes to 60-70% but it recovered easily). Googlebot ask at the moment of publication or 2-3 minutes later (the urls could be crawled sometimes 5 to 10 times at the same time for this new post). Maybe this makes the data base to freeze?? Also if after publishing we have some visitors.

    About the purging mechanisms, I said you I have FRONT PAGE – HOME PAGE – AUTHOR – POST TYPE – MENSUAL AND TERM ARCHIVE checked. But all the post are cleaned. I have a related article attached in all the post and also a lateral bar with recent post. If I have this options (the one who avoid recent post pages to be clean) unchecked why all the post are cleaned? Maybe if the only thing cleaned after posting is the home page and the new post (edited one for example) the cache problem could be solved (I could clean all at midnight when all is in calm as a solution) but as I said all post are cleaned although related post or recent post option is unchecked.

    Also I don’t know if server stale is working because it shouldnt be serving old versions while the new is created???

    Plugin Support qtwrk

    (@qtwrk)

    2 years, 6 months ago

    No , serve stale doesn’t work that way , it only works when multiple request to same page at same time , let’s say you have 10 requests to same page at same time , then first one will trigger the new cache generation while rest 9 of them will get stale cache , the condition to activate it is kind of hard to meet

    please try grab the purge log , on both versions so we can make compare and see if there is any difference

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

The topic ‘Lots of problem with last version when purging’ is closed to new replies.