Re: Perl/CGI + MySQL: How many calls is too many?

In broader terms of database performance, eWeek and PCMag just released some benchmarking on Oracle 9i, MySql 4.0.1 Max, MS SQL 2000, DB2, and Sybase's ASE. in an article Here.

Test included transactions, load testing, simultaneous requests, and more. Interesting article.

Spoiler:: MySql shone brightly...

"Overall, Oracle9i and MySQL had the best performance and scalability, with Oracle9i just very slightly ahead of MySQL for most of the run."

Plus, some tidbits and suggestions on tuning the brands they tested.

HTH

Comment on Re: Perl/CGI + MySQL: How many calls is too many?

Replies are listed 'Best First'.
Re: Re: Perl/CGI + MySQL: How many calls is too many? by Matts (Deacon) on Feb 27, 2002 at 21:47 UTC
Those benchmarks look pretty dodgy to me. Whenever I see these graphs where two products follow the EXACT same line on a graph (in this case MySQL and Oracle), then I get suspicious - it basically means that the database is running at the fundamental limits of "something", be it the OS or the driver or the technology being used. That's not necessarily a bad thing, but it tells you nothing about which is faster - MySQL or Oracle. For that you need the database itself be the limiting factor, and it's obviously not in this test.	[reply]
Re: Re: Re: Perl/CGI + MySQL: How many calls is too many? by mpeppler (Vicar) on Feb 27, 2002 at 22:18 UTC
Another issue for that particular test is that it seems that the JDBC drivers used played a big role. So while the app worked well for Oracle and MySQL it wasn't well suited for Sybase (Sybase isn't very good at handling cursors, because in general you don't need them...) Michael	[reply]


Pathologically Eclectic Rubbish Lister
	PerlMonks