Originally Posted by Mimi Gardenia
I only wonder why
there are server issues lately, more than anything else. I mean ,when Basenotes is slow loading or whatever... I usually go do something else . It's the 'mystery' that interests me.
The hourly regularity of this issue strongly indicates that this is an hourly cronjob being started on the server which is temporarily monopolizing either the disk drive or the CPU. If the server is a Unix/Linux machine, I would recommend running a process status at 15 seconds after the hour, and make sure the command includes flags to report both percentage CPU usage and in-process memory usage. Or, the command "top" (described here
) provides the information in a user-friendly format. If the server is a Windows machine, running the Task Manager and sorting the contents of the "Processes" tab by "CPU" and "Mem Usage" will accomplish the same thing. It's more than likely a CPU allocation problem. The type of error messages in the responses are clearly indicating that the listening socket is starving out HTTP connections while the CPU is busy with other processing, especially since it's very unlikely that there is an hourly drain on socket descriptor resources.
I was also seeing some time delays in connections to the doubleclick ad server, so doubleclick.com might also be having issues with an hourly cronjob which are slowing load times for BN pages. That will be harder to diagnose, since it's unlikely Google will allow anyone to run low-level diagnostic commands on their servers.