Why shouldn't IBM i be able to handle 100,000 concurrent non-stateful
users? In my mind it would only be the hardware that would limit the
capability - and potentially the TCP/IP routing if 100,000 connections
were in fact all coming in at exactly the same time. The latter part
I learned the hard way when doing some RPG web testing for a customer
of mine. We used JMeter to test a simple "hello world" app and were
able to send so many requests that the TCP/IP layer got overflowed
because Apache wasn't returning/releasing the socket handle quick
enough so the next request of the TCP/IP stack queue could be
processed. If you load enough into the TCP/IP queue it (the IBM i
server) will eventually just start rejecting requests. Turned out to
be a good way to know the limitations of the box (a small 520 running
V5R3).
Henrik, I get the feeling you think that IBMi is still mostly suited
for back office applications. I think it can work equally as well for
open-to-the-public type web sites. In fact, I am working on such a
project right now that deals with introducing a new social interaction
site that I will release as an article hopefully in November (my
effort at marketing the platform to non-IBMi companies/people).
Do I expect a 520 to handle 100,000 concurrent users? No. But I
should be able to scale up to that point with IBMi as long as the
other layers are also up to par (i.e. server's internet connection).
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Thu, Oct 7, 2010 at 10:16 AM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:
Who cares about 100.000 concurrent users, the iSeries is best known for
handling
not Facebook og Dating sites, but ERP solutions.
How many companies has 100.000 concurrent ERP users ?
2 ?
midrange.com
