Treasury explosion party
We're trying to debug a mysterious crash that happens when hundreds of simultaneous users all try to do basically the same thing at the same time, grab the open Treasury list spot.
Towards this effort, we organized an 'explosion party' which was met with great success. We had an explosion! We also were able to film it with metaphoric high-speed cameras. The sudden dip in the top graph shows a mass disconnection of all currently connected clients. The corresponding spikes in the middle and bottom graphs show both bandwidth and CPU rising sharply just after the disconnect.
Now to find and fix this annoying bug...
(it should also be noted that there are 20+ gigs of text log files to examine, definitely not appropriate for Flickr)
Treasury explosion party
We're trying to debug a mysterious crash that happens when hundreds of simultaneous users all try to do basically the same thing at the same time, grab the open Treasury list spot.
Towards this effort, we organized an 'explosion party' which was met with great success. We had an explosion! We also were able to film it with metaphoric high-speed cameras. The sudden dip in the top graph shows a mass disconnection of all currently connected clients. The corresponding spikes in the middle and bottom graphs show both bandwidth and CPU rising sharply just after the disconnect.
Now to find and fix this annoying bug...
(it should also be noted that there are 20+ gigs of text log files to examine, definitely not appropriate for Flickr)