I get your theory, but wouldn't the solution mean that you'll have to display a tweeter like message when the server is overloaded(the birds carrying a whale)? In such a case the user may not come back ever right? Like I gave up on tweeter when that happened twice. Regards.
Hi Skunks, Have been following the thread on the frustrations faced by KCPE candidates and parents when trying to access the results online and via SMS. This is not unique to KNEC, it happens all the time to ATM bridge systems, Online transactions processing, SMS Based systems especially of late the MPESA.
So what is the problem?
Very simple, designers and developers of these systems do not understand, are not aware or choose to ignore the Queue Theory principles!!
I will use a very simple example to illustrate the point. Imaging a queue in the bank waiting to be served by one cashier. If the policy of the bank is that a customer must be served within 10 mins, then the logical thing to do is to know when to turn away a customer who if they join the queue, will not be served within 10 mins. This is better than have all thousands of customers not served within 10 mins as per policy.......and will not kill the cashier!!
In short, it is time developers started taking queuing theory seriously when developing these kinds of systems.
Shad
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke