SQL Tests
2 отговора
183 прегледа
komentar za statiqta, koito prochetoh last week
citat
"This eWeek article benchmarks an impressive list of databases using JSP and BEA's WEbLogic Server: IBM's DB2 7.2 with FixPack 5, Microsoft Corp.'s SQL Server 2000 Enterprise Edition with Service Pack 2, MySQL AB's MySQL 4.0.1 Max, Oracle Corp.'s Oracle9i Enterprise Edition 9.0.1.1.1 and Sybase Inc.'s ASE (Adaptive Server Enterprise) 12.5.0.1.
However a closer look at the benchmarks reveals that the benchmark was highly skewed towards a particular software design (something that makes my tongue feel like duelling light-sabers: bidirectional updatable scrollable cursors), and JDBC drivers that were tuned for this approach performed very well (that is only Oracle and MySQL). So the benchmark was really about the quality of the JDBC drivers and NOT about the databases per se.
In the real world, for peak performance, developers have to code for the characteristics of the database they are using. So if you are using DB2, you code the DB2 way, not the Oracle way, not the eWeek benchmark way. This does hell to portability - but hey, that's the price for speed!
The other thing I find interesting is that ASP performance was better than using Java, though eWeek tries to downplay it. Given that PHP database performance tends to be better than ASP, comparing PHP and Java would have really been fun! -- John
"
"This eWeek article benchmarks an impressive list of databases using JSP and BEA's WEbLogic Server: IBM's DB2 7.2 with FixPack 5, Microsoft Corp.'s SQL Server 2000 Enterprise Edition with Service Pack 2, MySQL AB's MySQL 4.0.1 Max, Oracle Corp.'s Oracle9i Enterprise Edition 9.0.1.1.1 and Sybase Inc.'s ASE (Adaptive Server Enterprise) 12.5.0.1.
However a closer look at the benchmarks reveals that the benchmark was highly skewed towards a particular software design (something that makes my tongue feel like duelling light-sabers: bidirectional updatable scrollable cursors), and JDBC drivers that were tuned for this approach performed very well (that is only Oracle and MySQL). So the benchmark was really about the quality of the JDBC drivers and NOT about the databases per se.
In the real world, for peak performance, developers have to code for the characteristics of the database they are using. So if you are using DB2, you code the DB2 way, not the Oracle way, not the eWeek benchmark way. This does hell to portability - but hey, that's the price for speed!
The other thing I find interesting is that ASP performance was better than using Java, though eWeek tries to downplay it. Given that PHP database performance tends to be better than ASP, comparing PHP and Java would have really been fun! -- John
"