use the following search parameters to narrow your results:
e.g. sub:pics site:imgur.com dog
sub:pics site:imgur.com dog
advanced search: by author, sub...
~0 users here now
Please only post things related to the saidit website itself.
If you want a place to post any topic to the community, please post at /s/whatever or /s/worldnews
We are going to add more CPU cores to the saidit server to speed it up
submitted 2 months ago * by magnora7 from self.SaidIt
view the rest of the comments →
[–]x0x7 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - 2 months ago (0 children)
Determining the cpu level might be expensive per page render and any means that isn't isn't going to be very fine resolutioned and therefore would be resonant.
A solution would be to have a rolling array of the timestamps of each of the last 15 renders. If the oldest of the last 15 is very new then let the page cache longer. That's assuming you have a cache in the first place though.
Then basically you can set a maximum frequency that your rendering engine will work at that you know your cpu can't surpassed anyway so you might as well not queue the task, and just defer to cache for one more request.
If you were using nodejs I could show you how to do it.