This summary of test results is based on the averages of measurements obtained under heavy load (25 to 100 simultaneous users). The reason for omitting the lighter loads is to give each system the opportunity to reach its maximal potential, which makes the differences more pronounced than if the 'startup phase' had also been included. The numbers do not stand for pageviews per second like in the diagrams on the previous pages, but the total of what is achieved during a full ten minute run.
 |
 | Average performance MySQL 4.1.20 - concurrency 25+ |  |
 |
 | Woodcrest |   201337 |  |
 |
 | Opteron (DDR) |   179714 |  |
 |
 | Opteron (DDR2) |   162609 |  |
 |
 | Dempsey |   145327 |  |
 |
 | Dempsey-HT |   135615 |  |
 |
 | UltraSparc T1 |   92125 |  |
 |
 |
 | Average performance MySQL 5.0.20a - concurrency 25+ |  |
 |
 | Woodcrest |   217675 |  |
 |
 | Opteron (DDR) |   178866 |  |
 |
 | Opteron (DDR2) |   167101 |  |
 |
 | Dempsey |   153747 |  |
 |
 | Dempsey-HT |   121594 |  |
 |
 | UltraSparc T1 |   53997 |  |
 |
 |
 | Average performance PostgreSQL 8.2-dev - concurrency 25+ |  |
 |
 | Woodcrest |   295083 |  |
 |
 | Dempsey-HT |   264699 |  |
 |
 | Dempsey |   241023 |  |
 |
 | Opteron (DDR) |   219639 |  |
 |
 | Opteron (DDR2) |   216108 |  |
 |
 | UltraSparc T1 |   177907 |  |
 |
The tables below give the relative performance of Woodcrest, Dempsey, and Socket F. These are based on the same measurements as were used for the tables given above, and can be seen as percentual representations relating the performance of a single processor to the performance of the others. For example, the number 1.39 in the table below indicates that the Woodcrest offers 1.39 times the performance of Dempsey in MySQL 4.1.20, in other words, that it is 39% faster.
Woodcrest | MySQL 4.1.20 | MySQL 5.0.20a | PostgreSQL 8.2-dev | Average |
---|
Dempsey | 1.39 | 1,42 | 1,11 | 1.31 |
Opteron (DDR) | 1.12 | 1.22 | 1.34 | 1,23 |
Opteron (DDR2) | 1.24 | 1,30 | 1,37 | 1,30 |
UltraSparc T1 | 2.19 | 4.03 | 1.66 | 2.63 |
Dempsey | MySQL 4.1.20 | MySQL 5.0.20a | PostgreSQL 8.2-dev | Average |
---|
Woodcrest | 0.72 | 0.71 | 0.90 | 0.78 |
Opteron (DDR) | 0.81 | 0.86 | 1.21 | 0.96 |
Opteron (DDR2) | 0.89 | 0.92 | 1.22 | 1.01 |
UltraSparc T1 | 1.58 | 2.85 | 1.49 | 1.97 |
Socket F | MySQL 4.1.20 | MySQL 5.0.20a | PostgreSQL 8.2-dev | Average |
---|
Woodcrest | 0.81 | 0.77 | 0.73 | 0.77 |
Dempsey | 1.12 | 1.09 | 0.82 | 1.01 |
Opteron (DDR) | 0.9 | 0.93 | 0.98 | 0.94 |
UltraSparc T1 | 1.77 | 3.09 | 1.21 | 2.02 |
As a bonus, we take a look at the average performance per database. PostgreSQL, mostly thanks to its good scaling properties, gets scores that are over 50% higher than MySQL. The peeks of the two databases are closer together than the diagram below suggests, but because MySQL's performance degrades after the highest point while PostgreSQL retains more or less the same level, the difference gets bigger with 25 simultaneous users and more. To work out the averages, only Dempsey’s top scores have been taken into consideration, which means no HyperThreading for MySQL 4.1 and 5.0 and HyperThreading for PostgreSQL.
 |
 | Average performance per database |  |
 |
 | PostgreSQL 8.2-dev |   234687 |  |
 |
 | MySQL 4.1.20 |   156222 |  |
 |
 | MySQL 5.0.20a |   154277 |  |
 |