[QUOTE=ewmayer;519063]What other major forms of CPU bandwidth are in play here besides serving up pages? Database management, perhaps?[/QUOTE]I got the impression from Xyzzy's comments that it is other users on the shared host machine using up the CPU.

[quote]vBulletin Message
The server is too busy at the moment. Please try again later.


All times are UTC. The time now is 12:56.

Thu Jun 13 12:56:36 UTC 2019 up 5 days, 1:33, 6 users, load averages: 208.42, 80.57, 33.84[/quote]

As seems to happen with annoying frequency, in this instance the message appeared after I hit the "submit message" button to post, meaning everything I'd put in the message text window simply went bye-bye.

Luckily, I am in the habit of composing my messages in a text editor before hitting the "quote" or "post reply" buttons, and then pasting them in. I then hit "preview post" and try to catch the typos I inevitably make before hitting the "submit reply" button.

If I have made revisions in the text widow, and it just sits there after I hit "submit message," I assume it's going to boot me off with a "too busy" message, and copy the contents of the window and paste them into my text editor before they disappear into the void.

[QUOTE=Dr Sardonicus;519245]As seems to happen with annoying frequency, in this instance the message appeared after I hit the "submit message" button to post, meaning everything I'd put in the message text window simply went bye-bye.

Luckily, I am in the habit of composing my messages in a text editor before hitting the "quote" or "post reply" buttons, and then pasting them in. I then hit "preview post" and try to catch the typos I inevitably make before hitting the "submit reply" button.

If I have made revisions in the text widow, and it just sits there after I hit "submit message," I assume it's going to boot me off with a "too busy" message, and copy the contents of the window and paste them into my text editor before they disappear into the void.[/QUOTE]
Sometimes, as happened again this morning, initiating an in-browser edit is ok, but when saving the change the server is too busy, and there's a popup offering only one action, cancel posting the edit. Copying the edited post from browser edit box / paste to local text editor can work to save the edit for later retry, if done before accepting the cancel. Sometimes it takes a LOT of retries to get one edit posted. Fielding lots of attempts and serving up all those too-busy responses, for a single small edit that's being persistently blocked, take some resources too.

Yeah. I had just finished typing in my combined proofs of RH and P=NP when the server decided it was too busy to care and ate my submission.

I'm too lazy to type it all over again.

The margins on server capacity are too small to post the proofs here.
Same goes for the solution to practical fusion based electricity production, the cure for cancer, and proof of quantum gravity.

A new record for usage?
 

[quote]Sat Jul 6 14:26:24 UTC 2019 up 23 days, 1:19, 3 users, load averages: [b][color=red]249.79[/color][/b], 108.51, 48.2[/quote]:showoff:

:max:

rn
 

475 visitors with 461 "guests"

happy coincidences?