On Wed, Jul 29, 2009 at 9:26 AM, Ewald Horn <[email protected]> wrote:
> > Hi. > > Pardon my ignorance, but I need some help with the following : > > I'm tasked with selecting the hardware for a new web development, but > my experience mostly lies with MSSQL Server, and not MySQL or > PostgreSQL. > > The scenario is a web application, Java-based, of course, on Glassfish > 2.1, using either PostgreSQL or MySQL. I'm leaning towards PostgreSQL, > although I'm sure there are MySQL advocates out there that will have a > different opinion. The debate is not about the database though, but > about the server requirements. > > We will be experiencing about 1000 concurrent users, tables (not > complex) in excess of 20 million records each, and of course, a ton of > business logic in the back end. I've no clue what kind of hardware / > OS to specify, although I'm betting a *NIX operating system will be > preferred, to keep initial costs down and also to allow us to use > multiple processors and Gigs of RAM without additional licenses being > required. > > The primary concern that we have, is speed. In our humble experience, > SQL starts getting slow with huge numbers of records, and this > database will be growing, fast. Which OS would allow us the simplest > clustering capability and still be easy enough to learn within a very > short time-frame ? Based on the load mention(above) MySQL has better out-of-the-box clustering(I am told) than PostgreSQL, however I believe that this has improved in 8.4. Note that I am not a sysadmin, but have had interactions with them on various projects the clustering can be achieved via : 1: The application IE: Glassfish. 2: Apache sit infront of appserver and forward requests to the required server(multiple servers hosting the same application). 3: OS clustering, I'm not too familiar with them and have not worked on a project that has used it. 4: db clustering for backup and replication/load balancing. I think something to take into account with db and OS would be to do some due diligence(Good luck with that) IE: profile the system with the sort of load you would expect. Fair enough that there maybe no code, for the system, but see if they OS/db can handle the sort of load you are going to place on it. If the sql queries are slow part of the system(as mention earlier) have you used explain plans to optimize the sql? If you are going to multiple hardware vendors then this sort of testing should allow you to determine price/performance for the system. > > Thank you > Ewald Horn > > > > -- If you have something tough, give it to the Americans. If you have something difficult, give it to the Indians. If you have something impossible, give it to the Russians --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CTJUG Tech" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/CTJUG-Tech?hl=en For Cape Town Java User Group home page see http://www.ctjug.org.za/ For jobs see http://gamatamjobs.appspot.com/ -~----------~----~----~----~------~----~------~--~---
