Ok, I finally did it. I got my boss to slip a nice little application server in the budget. So here I am trying to spec out a nice Zope server. What should my priorities be when building this beast, I think we'll be able to spend about $10 Grand on this beast. We will be running a secure site using Apache and OpenSSL, and we are targeting about 100 continuous concurrent users. I have already set SOME priorities, because uptime is a big issue so the server will have redundant power supplies and hardware RAID 5. Beyond that, what do you suggest. Is memory more important than processor speed? Is it important to go with a Multi-processor server or will Zope/ Linux take advantage of a multi processor setup? Dream a little server for me :)
Oh boy... 10 Grand? IBM Netfinity 5500 M20 - Dual 700 MHz - 5 x 9.1 GB RAID 5 - 2 GB RAM - Dual NIC Cards - RH 6.1 Should be about 10 Grand. That thing is ROCK SOLID. It could eat 100 Concurrent users without a napkin. Can handle up to 4 GB RAM, 120+ GB of Drive and 4 Processors. Almost everything is hot swappable (power, fan, PCI) only time you would have to bring it down would be to so you could take it home. The other way to go would be to get 2 x Netfinity 5000 (Dual 700 MHz, 1 GB RAM, 3 x 9.1 GB RAID 5). Load balance them and you are golden. Enjoy... JMA
From: "Baker, Dennis (sjmr)" <DBaker@CHW.edu> Date: Tue, 21 Mar 2000 15:00:51 -0800 To: "'zope@zope.org'" <zope@zope.org> Subject: [Zope] Server Sizing
Ok, I finally did it. I got my boss to slip a nice little application server in the budget. So here I am trying to spec out a nice Zope server.
What should my priorities be when building this beast, I think we'll be able to spend about $10 Grand on this beast. We will be running a secure site using Apache and OpenSSL, and we are targeting about 100 continuous concurrent users. I have already set SOME priorities, because uptime is a big issue so the server will have redundant power supplies and hardware RAID 5.
Beyond that, what do you suggest. Is memory more important than processor speed? Is it important to go with a Multi-processor server or will Zope/ Linux take advantage of a multi processor setup?
Dream a little server for me :)
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Beyond that, what do you suggest. Is memory more important than processor speed? Is it important to go with a Multi-processor server or will Zope/Linux take advantage of a multi processor setup?
Zope, more correctly Python will not take advantage of a dual processor. I probably seriously consider buying a ZEO solution from DC. I don't know, but a ZEO solution might solve the problem with 100 continuous concurrent users writing to the ZODB? Regards, Johan Carlsson
Johan Carlsson wrote:
Beyond that, what do you suggest. Is memory more important than processor speed? Is it important to go with a Multi-processor server or will Zope/Linux take advantage of a multi processor setup?
Zope, more correctly Python will not take advantage of a dual processor.
Yes it will, it just won't scale exactly two fold. In almost all Python wrapped C calls, the C code releases the interpeter lock as often as possible, this allways happens, for example, when doing I/O or when calling database library routines. Two processors will give you a noticable benefit. Four or more will probably not. Further, Zope will not be the only process running, so a dual gives you the usual benefits, like doing a compile on one thing without killing your website.
I probably seriously consider buying a ZEO solution from DC. I don't know, but a ZEO solution might solve the problem with 100 continuous concurrent users writing to the ZODB?
ZODB FileStorage was not designed to be write intensive, the goal is to provide a mid-write high-read solution, this solution satisfies 99.9% of all web site needs. You would be surprised how much money you have to pay to Oracle to get, for example, their high write-write distributed database solutions (its in the six figures). ZEO is a distributed storage, but in the end it depends on a mechanism that actual writes the data somewhere. In the stock case, this is a FileStorage. If you want high-write intensity, consider a BerkeleyStorage (which works fine as the backend for ZEO) or offload alot of your high-write intensive data to a relational database. -Michel
participants (4)
-
Baker, Dennis (sjmr) -
J. Atwood -
Johan Carlsson -
Michel Pelletier