SV: [PHP] Stressing out db connections

If you can afford Oracle8i, with a big amount of users, the hardware is cheap.. If your running Oracle serious, purchase 4-5 SCSI disks. And the most important thing of all, use Oracle Connection manager (included in the Oracle package) to reduce connections to the database. Things that are good too have if your running Oracle: * Oracle DBA course. * Oracle support. -----Ursprungligt meddelande----- Från: Jonathan Chum [mailto:jchum@techdevelopers.com] Skickat: den 6 augusti 2000 19:45 Till: August Zajonc; php-general@lists.php.net Ämne: RE: [PHP] Stressing out db connections Thanks for the lengthy reply. I have already gotten a few emails that I should just skip MySQL and go with Oracle. I'm pretty glad my friend purchased the Oracle 8i for LINUX kit. Only a matter of setting the software up which is quite daunting. I was reading I believe a RedHat HOW TO which says that Oracle will need at least 128MB RAM though. Have you had any experience though with a dedicated server provider? Would they be able to install Oracle if I sent the CDs, or would they'd require me to install them? There is sure alot of CDs that came with the kit. Also, you say that MySQL can handle 1,000 initial connections or 4 web servers. Are you saying that each server could handle a specific amount of connections? Just for clarity although I'm pretty much sold to setting up Oracle to handle the project I'm working on. I've heard of Interbase as a solid database engine also, but I sort of fell in love with Oracle when I heard that Yahoo was powered by it. I really wonder what powers up Google's backend. They crawl sites from top to bottom and not just meta tags. I would figure that an average sites has at least 10-15KB of text once the HTML is stripped out. A query on "<HTML>" on the google.com engine brings out a fourth of the entire database in seconds. Anyway, after hearing somewhere that Oracle powers Yahoo, I persuaded a friend to purchase it just fun of experimenting with it. I guess the money maybe, well worth it. Regards, Jonathan Chum At 12:06 PM 8/6/2000 -0400, August Zajonc wrote: >I'd recommend taking the oracle route. There is currently no good connection >pooling for MySQL, you'll be limited at least initially to 1000 connections, >or 4 web servers... You can patch the source of a bunch of libraries and >begin to expand that, but you'll begin to run into problems as your key >cache gets larger (I can't safely bump mine beyond 256MB) and we at least >experience index corruption pretty regularly though this may be our >situation alone which under MySQL requires a DB shutdown to fix. > >Many users have reported solid reliability. I suspect some of it ties to the >fact that we run pretty high loads under SMP, MySQL was rock solid stable >for us at the 100 query per second range. > >One issue you need to look at his how well the DB can scale. If you are >extremely successful, and it sounds like you will be, you won't care as much >about how fast it is at small workloads, but would willing pay a little to >have to handle the higher loads. > >If you go with Oracle I'd love to hear your experiences with it. Once nice >thing sticking with MySQL (and sending some of that Oracle money to the >developers) is that it is GPL, something that is fun and improves the world >for everyone, including those of us who can't afford oracle servers yet. > >I don't know of any MySQL showcase installations on the higher end (10,000 >connections, 10,000 queries/second) but they are getting there. > >Finally, there are some interesting contenders out there in Postgre and >Interbase, though no one has published good comparisons of them yet. Here's >hoping. Interbase can run in SuperServer mode where it doesn't suck up a lot >of processes to handle the connections. > >August > > > >-----Original Message----- >From: Jonathan Chum [mailto:jchum@techdevelopers.com] >Sent: Sunday, August 06, 2000 9:49 AM >To: php-general@lists.php.net >Subject: [PHP] Stressing out db connections > > >I have worked on many small sites and now time is calling me for a >high-usage site. Right now, we have a PII 400 with 64 MB PC133 RAM on >Redhat 6.2 which will be used to jump start the site. What I want to >know is how much connections to the database can be handled at once on >the server, or perhaps some tips with the hardware architecture or >software architecture would be much grateful. > >The site is a forum based site with over 1 million members at the >start and increasing rapidly. What I also want to know what DB would >be more suitable for the job, Oracle or MySQL? I have both and have >written much of the forum software in MySQL which I don't think will >be a big tuffy to convert over to Oracle. I hear that Oracle takes a >great amount of RAM though just for the installation. Yet, in the long >run, will Oracle should be my choice to power multiple boards with >multiple users connected to a database simultaneously? > >Thanks for any help or insights you can give to me. > >-- >PHP General Mailing List (http://www.php.net/) >To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net >For additional commands, e-mail: php-general-help@lists.php.net >To contact the list administrators, e-mail: php-list-admin@lists.php.net -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net