Around 12.00 we managed to load and analyze upto 100 mczs/minute from
Smalltalkhub.
We hoped that we would not be able to overload Smalltalkhub from a home ADSL
connection, using a single (non multi-threaded) Moose image.
However, this seems to coincide with some failing jenkins builds. We
On 18 September 2013 13:18, Stephan Eggermont step...@stack.nl wrote:
Around 12.00 we managed to load and analyze upto 100 mczs/minute from
Smalltalkhub.
We hoped that we would not be able to overload Smalltalkhub from a home
ADSL
connection, using a single (non multi-threaded) Moose image.
Igor wrote:
i think you should contact Nico about how to run tests
using some test server first, and only if it passes, on deployed one :)
Oh, the code was working fine ;) Really no different to copying
monticello packages from one repo to another. It's just that
I try to find all invocations in
On 18 Sep 2013, at 17:19, Igor Stasenko siguc...@gmail.com wrote:
On 18 September 2013 13:18, Stephan Eggermont step...@stack.nl wrote:
Around 12.00 we managed to load and analyze upto 100 mczs/minute from
Smalltalkhub.
We hoped that we would not be able to overload Smalltalkhub from
Sven wrote
StHub is an important shared community resource.
Definitely.
And this is a stop-the-line problem.
Having a single image on an ADSL connection bring down
smalltalkhub doing one mcz request at a time means there is a
serious dos risk.
This is my packagecache from the offending run:
