Well I either pressed the magic button, or GoDaddy patched whatever they broke...
here is a load graph of the past week - they rolled out a patch on 5/16 for a server side security issue.
(they scan websites for malware, so if it gets uploaded, they delete it.)
The first graph is concurrent requests, the second is processes (one request can spawn multiple processes, a DB lookup, template->webpage, fetching last login, etc)
The higher the load, the slower the service time until it throws a fault because the requests arrive much faster than they can be served.
(I know you all love queuing theory, there is one line, and multiple servers)
So I did a few things to reduce requests, but not so much that it should change the arrival all at once at 3am EDT.
Time is in PDT on chart - we'll see.
here is a load graph of the past week - they rolled out a patch on 5/16 for a server side security issue.
(they scan websites for malware, so if it gets uploaded, they delete it.)
The first graph is concurrent requests, the second is processes (one request can spawn multiple processes, a DB lookup, template->webpage, fetching last login, etc)
The higher the load, the slower the service time until it throws a fault because the requests arrive much faster than they can be served.
(I know you all love queuing theory, there is one line, and multiple servers)
So I did a few things to reduce requests, but not so much that it should change the arrival all at once at 3am EDT.
Time is in PDT on chart - we'll see.
