This is a good question. I don't have experience by myself but I can tell you what I think it is usually done: 1) For one CPU: If the image don't need to be saved (no need of in image persistence) you can take the same VM and load N number of images running at the same .image. You can even not use .changes and .sources. Each image in different port. Then, you have in front of them a web server (Apache or friends) and you do load balance. The only thing you should take care with Seaside is to have AFFINITY -> the same client should go always to the same image while a conversation occurs. This is just a web-server setting. 2) For multiple core, I am thinking, maybe I am wrong, you may be able to load different vms. For assigning each VM to a particular CPU. I don't know windows, but in Linux (maybe I am wrong) I think you can specify where to exclusively run a process. The, for each VM you do 1). Do you know if this can work? Finally, there are different VM that aim not necessary multiple CPU but similar: - COG VM - Hydra I cc'ed may developers of them so that they can help you. Cheers Mariano 2010/5/24 Andrei Stebakov <lispercat@gmail.com>
I've been really impressed with what Seaside and Pier were capable of and really wanted to start my new web project with Pharo. I learned that Pharo (and most other open source ST implementations) only use green threads, having no ability to use a multi-core CPU systems. For those of you with experience building mid to heavy load web sites, how do you expect them to scale up on using just one core? Is Pharo a right tool for that? Maybe Pharo (Squeak) has something up its sleeve to handle this, but my heart really sank when I learned about this issue...
Thank you, Andrei
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project