I couldn't find any good sizing figurs, so I try it this way...
When using a midrange server for gateway and one for portal, with each one
cpu and 1GB memory.... how many concurrent users will this setup support ?
Other sizing figures are welcome too :)
TIA
Stephen Trap
I hate to say this, but it depends on a lot of things. In the limited
testing I've done with iPS-SP3 the SSL performance of the gateway is the
limiting factor. This has greatly improved in SP3, but on our site, I can
overload a single gateway with 20 simultaneous users. Since the session is
maintained by the server, it wasn't too difficult to load balance over a
number of gateways to get the number of transactions up to over 100
simultaneous users.
I know this is vague, but there's a lot of factors that are specific to your
setup:
- Are you running a secure portal? Do you need to ?
- Is your portal site processing intensive with dynamic content ?
- What is the processing speed of your servers ?
as well as many others.
I'm not sure what you're considering for a mid-range server, but you need to
know that while the gateway is multi-threaded it only uses one CPU per
instance. A big multiprocessor machine won't buy you much scalability there.
I'd recommend a server with the fastest CPU available as SSL is processor
intensive. The Portal Server runs a number of processes so a multi-processor
system will benefit you there, however, even under heavy stress loads, the
Portal Server was rarely overloaded due to the bottleneck in the gateway.
These views are from my experience with a specific implementation, your
mileage may vary.
"Stephen Trap" <stephen.trap@eurasp.com> wrote in message
news:9oc10b$7ph1@ripley.netscape.com...
> I couldn't find any good sizing figurs, so I try it this way...
> When using a midrange server for gateway and one for portal, with each one
> cpu and 1GB memory.... how many concurrent users will this setup support ?
> Other sizing figures are welcome too :)
>
> TIA
> Stephen Trap
>
>
>
