Hi!
I don't have any experience in deploying apps with such a large
user base. But from what I understand from your text, you are telling
that you want to handle 500.000 concurrent users on each server,
right? I would say forget it... Apple makes technology, not miracles! ;)
Yours
Miguel Arroz
On 2006/05/23, at 22:27, [EMAIL PROTECTED] wrote:
Hi;
I'm new to the list so excuse me if this had been discussed before.
A partner of my company is planning to develop a webobjects based
application that is going to serve to about 7-8 million users over
client application. There will be about 1 million concurrent active
users nation wide in the average case.
So far I've planned to divide the users into several regions(7
regions -
1 million users/region). There will be at least 1 apache server(dual
processor G5 XServe) and 2 webobjects app server (Xserve dual
processor
G5 too). Leaving the network infrastructure, database and backup
apart
do you think it is feasible? Do you happen to have any idea about
approximetely how many threads per server and how many servers will be
enough for this project?
Our current G4 Xserve running both apache and wo sometimes fails when
more than say 100 hundred users are transacting over our online store.
So I have serious doubts.
Thanks in advance
Mert Yentur
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/arroz%
40guiamac.com
This email sent to [EMAIL PROTECTED]
"I felt like putting a bullet between
the eyes of every Panda that wouldn't
scr*w to save its species." -- Fight Club
Miguel Arroz
http://www.ipragma.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
