[Seaside] Server sizing - 100 concurrent users

[Boris Popov]

[Disclaimer: VisualWorks]

There are also plenty of things that block the VM on occasion, for
instance our RSA auth calls sometimes take upwards of 3 seconds during
which time VM is waiting for external call to return, so having less
users per VM helps substantially if we want to provide as much of a
seamless experience as possible.

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Jason Johnson
> Sent: Friday, June 08, 2007 12:46 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Server sizing - 100 concurrent users
> 
> radoslav hodnicak wrote:
> >
> > What's the point of having 10-20VMs (not sure whether you mean
virtual
> > machines as in OS virtualization or squeak's VM) on a single server?
I
> > would understand having 2-4 (one image per cpu/core).
> >
> > rado
> 
> 
> Well having more doesn't hurt.  For example, now that Erlang uses
native
> threads to create extra VMs you can configure how many to create.
From
> what I have seen they tend to get the best numbers with 3 or 4 per
CPU,
> not 1 per.
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside