Concurrency & Scalability

[Siyaram Singh]

Hi,
We are using Web sphere 4.0.3 App Server and Sun Solaris 2.8 OS. Our application needs to support 1000 cocurrent user.
Our J2EE application contains Session Beans, CMP AND POJO.
Can U pls insight us:
How many Server Clones we should have to address 1000 Users Concurrently?
Should I go for vertical Cloning or Horizontal Cloning ? If Yes pls give some details ?

Thanks in Advance,
SS

[bharat nagpal]

I won't advice you to go only for Vertical cloning, as horizontal cloning gives you failover support. So the combination of 2 would be a better approach.The exact configuration depends on many aspects like your data access, dynamic stuff and appraoch followed while development. Any other ideas?

[Siyaram Singh]

Hi Bharat,
Thanks for suggestion!
I wanted to know the No of Concurrent Executable threads for WebSphere 4.0.3. Based on it we can analyse the concurrent users and config.

Thanks
SS

[Kyle Brown]

WebSphere's threads are not your problem. The problem is whether or not your HARDWARE will support the number of users you require.
You need to read (carefully, from cover to cover) the Websphere version 5.0 performance and scalability handbook redbook, and Stacy Joines' book "Performance Analysis for Java Websites". After you've read and understood those you're ready to do capacity planning and set up a scalable network.
Kyle

[Siyaram Singh]

Hi kyle,
Suppose we have to support certain xxxx Councurrent users and yyyy response time for diffrent functinality for an application. Response time is based on the nature of request / transaction.
Suppose J2EE application is using three tier architecture and WebSphere App server and Oracle database. How we will plan for Hardware Config ???
Hardware system ??
No of Proceessor ?
RAM Capacity ?
Harddisk ?
to acheive the optimmum performance.
Regards,
Siyaram

[Kyle Brown]

As I said in the previous post this is NOT something that you can answer in a single post. This is a complicated, involved subject. Luckily it has been well, and definitively covered in Stacy Joines' book.
Kyle