Note that there are some explanatory texts on larger screens.

plurals
  1. POHow exactly warmup requests works?
    primarykey
    data
    text
    <p>we have observed a strange behaviour of loading requests that we would like to share to obtain a precise answer.</p> <p>We enabled the warmup request handler from the day of introduction because loading requests take from 15 to 25 seconds.</p> <p>We always used the old "always-on" feature and then we configured the "Idle Instances" slider in "Application Settings" to 1-Automatic (1 reserved instance) under the new billing system.</p> <p>Everything worked well because the majority (not all, but this is documented) of loading requests were correctly routed to /<em>ah</em>/warmup.</p> <p>Our application is used only during work times in Italy so that single reserved instance wastes money during the night and the weekends, so we decided, two weeks ago, to try to move the "Idle Instances" slider settings to Automatic-Automatic.</p> <p>The bill decreased, but after that <em>all</em> the loading request are front facing request (or at least task queues/cron requests). In that two weeks in our logs the /_ah/warmup is <em>totally</em> disappeared.</p> <p>After two weeks, we decided to revert the slider setting to 1-Automatic and the next loading request was on /_ah/warmup. Now we are stuck on 1-Automatic.</p> <p>We searched the official documentation for this behaviour but we found nothing about it.</p> <p>We found only this question <a href="https://stackoverflow.com/questions/10875460/reserved-instances-and-warmup-requests-not-working">Reserved instances and warmup requests not working</a> that states the same thing.</p> <p>So the /_ah/warmup servlet is supposed to be totaly useless when the "Idle Instances" settings is on Automatic-Automatic? Or there is something wrong in our application?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload