best way to cope with peaks in traffic - sr-users

26 Oct 2014

Gents,

assuming we don't use async methods (I know, it's against fashion),
eventually you'll end up in having some bottlenecks in your config...

Now thanks to a lot of children you can easily work around this, a maximum
of 32 children gives you already quite something, and if you use the
dispatcher, you can ramp that up to quite some capacity. ;)

Now, there are moments where still limits are passed, so what would be the
best way to keep your system healthy?

I was thinking in the direction of using a hashtable value or $var to keep
track of the children in use and e.g. if 31 children are used, refuse to
process the 32th request (assuming 32 children are setup).  Would this be a
valid strategy? Or am I overthinking?

Grtz,

Davy