Buzzsg4 and Thread Notifications

[ToolOutfitters]

First of all, is the server reboot going to be a daily occurrence? Reboot, reboot, found problem, fixed problem, reboot, etc...

Also, why is the thread notification not being sent until 6-7 hours after it has been posted?

[Vitaliy K.]

First of all, is the server reboot going to be a daily occurrence? Reboot, reboot, found problem, fixed problem, reboot, etc...

Also, why is the thread notification not being sent until 6-7 hours after it has been posted?

We have already localized the problem on this server and have taken the measures to prevent overload issues from re-occurring.

As for thread notifications, they are being sent immediately after a reply or a thread is posted. The problem might be related to the fact that after you receive a thread notification, you will not receive any more notifications related to this forum thread until you visit the forum again.

[ToolOutfitters]

The notifications that I am receiving are 6-7 hours after the thread was started.

[Matt R.]

We actually have a new and improved notification system launching in a few weeks (as a result of user feedback).

[ToolOutfitters]

I know yall have your hands full with DDOS attacks on other servers but Buzzsg4 is continuing to experiencing high server loads.

Server Load 8.88 (16 cpus)

[Tony]

If there's really 16 cpus in that sucker (?) then a load of 8 is fine. The limit is 1.0 per cpu - indicating the cpus are being used 100% and commands are being queued.

[ToolOutfitters]

If there's really 16 cpus in that sucker (?) then a load of 8 is fine. The limit is 1.0 per cpu - indicating the cpus are being used 100% and commands are being queued.

That's what it was reading after the stats page took a minute to load. Who knows what it was previously.