Did many local access records in the log cause server downtime?

  • Resolved zhanhongyuan

    (@zhanhongyuan)


    1 year, 2 months ago

    I am quite certain that I have encountered this issue, which is quite serious, so I would like to know how to set the frequency of preloading. I found that the access records of this machine are very regular in the log, with one request per second and two UAs used:
    Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1
    Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
    I would like to know if this is the effect of plugin preloading. If so, I would like to reduce the frequency or let you know how often this preloading is executed?
    Question 2: After the cache content expires, will these expired cache files be automatically cleared and new files be immediately re cached? If so, what is the frequency of execution? If we don’t immediately re cache, but instead execute the re caching of files according to the pre loaded settings or pre loaded schedule?

    My ai tools site URL: https://www.popai.pro/resources/ai-tools/how-to-add-more-samples-to-krita-ai-generation-tool/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Damilare

    (@deabiodun)

    1 year, 2 months ago

    Hi @zhanhongyuan!

    I would like to know how to set the frequency of preloading

    You can set the the frequency of preloading using the scheduled preloader at WP-Optimize > Cache > Preload. Simply activate the option and choose your schedule type.

    I found that the access records… I would like to know if this is the effect of plugin preloading.

    The frequent access records you’ve seen cannot be from the preloading feature as the preloader only runs as scheduled and does not run indefinitely. I will suggest you look into such frequent requests as they could be from bad actors.

    Regarding cache, expired cache files are automatically cleared. The frequency of execution depends on the trigger for clearing the previous cache.

    Let us know if you need further clarification.

    Thanks.

    Thread Starter zhanhongyuan

    (@zhanhongyuan)

    1 year, 2 months ago

    I feel like you misunderstood my meaning. My preloader hasn’t been executing all the time, it’s just executing the preloading task within a certain period of time. give an example:
    Preloading execution tasks are within the daily scope, and the specific request for executing preload tasks is 2 per second, not the frequency cycle of executing preload tasks every day. Can you understand my description?
    If there are no issues, I will continue to describe:
    I would like to know where I can modify this execution preload task to 1 request per second, if available? Because the current frequency of task execution can cause abnormal situations on the site.
    In addition, I would like to know if publishing new posts will result in longer backend processing tasks for the site. I am using the website backend normally and the speed is very fast. But when posting, you have to wait for 1 minute to complete the posting. Is this situation normal?

    Thread Starter zhanhongyuan

    (@zhanhongyuan)

    1 year, 2 months ago

    Also need to confirm: if the preloading function is enabled: Generate separate files for mobile devices， Will the mobile page be preloaded?

    Plugin Support vupdraft

    (@vupdraft)

    1 year, 2 months ago

    – Using add_filter(‘wpoptimize_preload_delay’, ‘my_preload_delay_method’), you can override the delay between two pages, which is currently set at 500000 (1/2 a second).

    – Using add_filter(‘wpo_page_cache_preload_memory_threshold’, 10485760);
    That filter lets you change how much memory should be left before interrupting the preload queue (10MB by default).

    Mobile pages will be preloaded

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

The topic ‘Did many local access records in the log cause server downtime?’ is closed to new replies.