Skip to content

H
h2database
切换分支/标签
查找文件
Normal viewHistoryPermalink
performance.html 22.1 KB
Newer Older
Thomas Mueller's avatar
--no commit message
35e27cd5
 
Thomas Mueller committed
1 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
2 
<!--
Thomas Mueller's avatar
add eclipse public license
2ed183fb
 
Thomas Mueller committed
3 4 5 
Copyright 2004-2008 H2 Group. Multiple-Licensed under the H2 License, Version 1.0,,
and under the Eclipse Public License, Version 1.0
(http://h2database.com/html/license.html).
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
6 7 
Initial Developer: H2 Group
-->
Thomas Mueller's avatar
--no commit message
35e27cd5
 
Thomas Mueller committed
8 9 
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /><title>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
10 
Performance
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
11 
</title><link rel="stylesheet" type="text/css" href="stylesheet.css" />
Thomas Mueller's avatar
The documentation no longer uses a frameset (except the Javadocs).
20d71e3b
 
Thomas Mueller committed
12 
<!-- [search] { -->
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
13 14 15 
<script type="text/javascript" src="navigation.js"></script>
</head><body onload="frameMe();">
<table class="content"><tr class="content"><td class="content"><div class="contentDiv">
Thomas Mueller's avatar
The documentation no longer uses a frameset (except the Javadocs).
20d71e3b
 
Thomas Mueller committed
16 
<!-- } -->
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
17 18 19 

<h1>Performance</h1>
<a href="#performance_comparison">
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
20 
    Performance Comparison</a><br />
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
21 22 
<a href="#poleposition_benchmark">
    PolePosition Benchmark</a><br />
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
23 
<a href="#application_profiling">
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
24 
    Application Profiling</a><br />
Thomas Mueller's avatar
--no commit message
755bd88a
 
Thomas Mueller committed
25 26 
<a href="#database_profiling">
    Database Profiling</a><br />
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
27 
<a href="#database_performance_tuning">
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
28 
    Performance Tuning</a><br />
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
29
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
30 
<br /><a name="performance_comparison"></a>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
31 
<h2>Performance Comparison</h2>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
32 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
33 
In most cases H2 is a lot faster than all other
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
34 
(open source and not open source) database engines.
Thomas Mueller's avatar
--no commit message
927afe2d
 
Thomas Mueller committed
35 
Please note this is mostly a single connection benchmark run on one computer.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
36 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
37 38 39 40 

<h3>Embedded</h3>
<table border="1" class="bar">
<tr><th>Test Case</th><th>Unit</th><th>H2</th><th>HSQLDB</th><th>Derby</th></tr>
Thomas Mueller's avatar
--no commit message
0dfee241
 
Thomas Mueller committed
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 
<tr><td>Simple: Init</td><td>ms</td><td>719</td><td>1344</td><td>2906</td></tr>
<tr><td>Simple: Query (random)</td><td>ms</td><td>328</td><td>328</td><td>1578</td></tr>
<tr><td>Simple: Query (sequential)</td><td>ms</td><td>250</td><td>250</td><td>1484</td></tr>
<tr><td>Simple: Update (random)</td><td>ms</td><td>688</td><td>1828</td><td>14922</td></tr>
<tr><td>Simple: Delete (sequential)</td><td>ms</td><td>203</td><td>265</td><td>10235</td></tr>
<tr><td>Simple: Memory Usage</td><td>MB</td><td>6</td><td>9</td><td>11</td></tr>
<tr><td>BenchA: Init</td><td>ms</td><td>422</td><td>672</td><td>4328</td></tr>
<tr><td>BenchA: Transactions</td><td>ms</td><td>6969</td><td>3531</td><td>16719</td></tr>
<tr><td>BenchA: Memory Usage</td><td>MB</td><td>10</td><td>10</td><td>9</td></tr>
<tr><td>BenchB: Init</td><td>ms</td><td>1703</td><td>3937</td><td>13844</td></tr>
<tr><td>BenchB: Transactions</td><td>ms</td><td>2360</td><td>1328</td><td>5797</td></tr>
<tr><td>BenchB: Memory Usage</td><td>MB</td><td>8</td><td>9</td><td>8</td></tr>
<tr><td>BenchC: Init</td><td>ms</td><td>718</td><td>468</td><td>5328</td></tr>
<tr><td>BenchC: Transactions</td><td>ms</td><td>2688</td><td>60828</td><td>7109</td></tr>
<tr><td>BenchC: Memory Usage</td><td>MB</td><td>10</td><td>14</td><td>9</td></tr>
Thomas Mueller's avatar
--no commit message
b09fd536
 
Thomas Mueller committed
56 
<tr><td>Executed Statements</td><td>#</td><td>594255</td><td>594255</td><td>594255</td></tr>
Thomas Mueller's avatar
--no commit message
0dfee241
 
Thomas Mueller committed
57 58 
<tr><td>Total Time</td><td>ms</td><td>17048</td><td>74779</td><td>84250</td></tr>
<tr><td>Statement per Second</td><td>#</td><td>34857</td><td>7946</td><td>7053</td></tr>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
59 60 61 62 63 
</table>

<h3>Client-Server</h3>
<table border="1" class="bar">
<tr><th>Test Case</th><th>Unit</th><th>H2</th><th>HSQLDB</th><th>Derby</th><th>PostgreSQL</th><th>MySQL</th></tr>
Thomas Mueller's avatar
--no commit message
0dfee241
 
Thomas Mueller committed
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 
<tr><td>Simple: Init</td><td>ms</td><td>2516</td><td>3109</td><td>7078</td><td>4625</td><td>2859</td></tr>
<tr><td>Simple: Query (random)</td><td>ms</td><td>2890</td><td>2547</td><td>8843</td><td>7703</td><td>3203</td></tr>
<tr><td>Simple: Query (sequential)</td><td>ms</td><td>2953</td><td>2407</td><td>8516</td><td>6953</td><td>3516</td></tr>
<tr><td>Simple: Update (random)</td><td>ms</td><td>3141</td><td>3671</td><td>18125</td><td>7797</td><td>4687</td></tr>
<tr><td>Simple: Delete (sequential)</td><td>ms</td><td>1000</td><td>1219</td><td>12891</td><td>3547</td><td>1938</td></tr>
<tr><td>Simple: Memory Usage</td><td>MB</td><td>6</td><td>10</td><td>14</td><td>0</td><td>1</td></tr>
<tr><td>BenchA: Init</td><td>ms</td><td>2266</td><td>2484</td><td>7797</td><td>4234</td><td>4703</td></tr>
<tr><td>BenchA: Transactions</td><td>ms</td><td>11078</td><td>8875</td><td>26328</td><td>18641</td><td>11187</td></tr>
<tr><td>BenchA: Memory Usage</td><td>MB</td><td>8</td><td>13</td><td>10</td><td>0</td><td>1</td></tr>
<tr><td>BenchB: Init</td><td>ms</td><td>8422</td><td>12531</td><td>27734</td><td>18609</td><td>12312</td></tr>
<tr><td>BenchB: Transactions</td><td>ms</td><td>4125</td><td>3344</td><td>7875</td><td>7922</td><td>3266</td></tr>
<tr><td>BenchB: Memory Usage</td><td>MB</td><td>9</td><td>10</td><td>8</td><td>0</td><td>1</td></tr>
<tr><td>BenchC: Init</td><td>ms</td><td>1781</td><td>1609</td><td>6797</td><td>2453</td><td>3328</td></tr>
<tr><td>BenchC: Transactions</td><td>ms</td><td>8453</td><td>62469</td><td>19859</td><td>11516</td><td>7062</td></tr>
<tr><td>BenchC: Memory Usage</td><td>MB</td><td>10</td><td>15</td><td>9</td><td>0</td><td>1</td></tr>
Thomas Mueller's avatar
--no commit message
b09fd536
 
Thomas Mueller committed
79 
<tr><td>Executed Statements</td><td>#</td><td>594255</td><td>594255</td><td>594255</td><td>594255</td><td>594255</td></tr>
Thomas Mueller's avatar
--no commit message
0dfee241
 
Thomas Mueller committed
80 81 
<tr><td>Total Time</td><td>ms</td><td>48625</td><td>104265</td><td>151843</td><td>94000</td><td>58061</td></tr>
<tr><td>Statement per Second</td><td>#</td><td>12221</td><td>5699</td><td>3913</td><td>6321</td><td>10235</td></tr>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
82 83 84 85 86 
</table>

<h3>Benchmark Results and Comments</h3>

<h4>H2</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
87 
<p>
Thomas Mueller's avatar
--no commit message
0dfee241
 
Thomas Mueller committed
88 
Version 1.0.67 (2008-02-22) was used for the test.
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
89 90 91 92 93 94 95 96 
For simpler operations, the performance of H2 is about the same as for HSQLDB.
For more complex queries, the query optimizer is very important.
However H2 is not very fast in every case, certain kind of queries may still be slow.
One situation where is H2 is slow is large result sets, because they are buffered to
disk if more than a certain number of records are returned.
The advantage of buffering is, there is no limit on the result set size.
The open/close time is almost fixed, because of the file locking protocol: The engine waits
20 ms after opening a database to ensure the database files are not opened by another process.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
97 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
98 99 

<h4>HSQLDB</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
100 
<p>
Thomas Mueller's avatar
--no commit message
dfbbf263
 
Thomas Mueller committed
101 
Version 1.8.0.8 was used for the test.
Thomas Mueller's avatar
--no commit message
9d0f0920
 
Thomas Mueller committed
102 103 
Cached tables are used in this test (hsqldb.default_table_type=cached),
and the write delay is 1 second (SET WRITE_DELAY 1).
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
104 105 106 
HSQLDB is fast when using simple operations.
HSQLDB is very slow in the last test (BenchC: Transactions), probably because is has a bad query optimizer.
One query where HSQLDB is slow is a two-table join:
Thomas Mueller's avatar
--no commit message
e59d810e
 
Thomas Mueller committed
107 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
108 109 110 111 112 
<pre>
SELECT COUNT(DISTINCT S_I_ID) FROM ORDER_LINE, STOCK
WHERE OL_W_ID=? AND OL_D_ID=? AND OL_O_ID&lt;? AND OL_O_ID>=?
AND S_W_ID=? AND S_I_ID=OL_I_ID AND S_QUANTITY&lt;?
</pre>
Thomas Mueller's avatar
--no commit message
e59d810e
 
Thomas Mueller committed
113 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
114 115 116 
The PolePosition benchmark also shows that the query optimizer does not do a very good job for some queries.
A disadvantage in HSQLDB is the slow startup / shutdown time (currently not listed) when using bigger databases.
The reason is, a backup of the database is created whenever the database is opened or closed.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
117 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
118 119 

<h4>Derby</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
120 
<p>
Thomas Mueller's avatar
--no commit message
dfbbf263
 
Thomas Mueller committed
121 
Version 10.3.1.4 was used for the test. Derby is clearly the slowest embedded database in this test.
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
122 
This seems to be a structural problem, because all operations are really slow.
Thomas Mueller's avatar
--no commit message
b09fd536
 
Thomas Mueller committed
123 
It will not be easy for the developers of Derby to improve the performance to a reasonable level.
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
124 
A few problems have been identified: Leaving autocommit on is a problem for Derby.
Thomas Mueller's avatar
--no commit message
cb967665
 
Thomas Mueller committed
125 
If it is switched off during the whole test, the results are about 20% better for Derby.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
126 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
127 128 

<h4>PostgreSQL</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
129 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
130 131 132 133 
Version 8.1.4 was used for the test.
The following options where changed in postgresql.conf:
fsync = off, commit_delay = 1000.
PostgreSQL is run in server mode. It looks like the base performance is slower than
Thomas Mueller's avatar
--no commit message
9d0f0920
 
Thomas Mueller committed
134 
MySQL, the reason could be the network layer.
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
135 
The memory usage number is incorrect, because only the memory usage of the JDBC driver is measured.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
136 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
137 138 

<h4>MySQL</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
139 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
140 141 142 143 144 145 146 147 148 149 150 
Version 5.0.22 was used for the test.
MySQL was run with the InnoDB backend.
The setting innodb_flush_log_at_trx_commit
(found in the my.ini file) was set to 0. Otherwise (and by default), MySQL is really slow
(around 140 statements per second in this test) because it tries to flush the data to disk for each commit.
For small transactions (when autocommit is on) this is really slow.
But many use cases use small or relatively small transactions.
Too bad this setting is not listed in the configuration wizard,
and it always overwritten when using the wizard.
You need to change this setting manually in the file my.ini, and then restart the service.
The memory usage number is incorrect, because only the memory usage of the JDBC driver is measured.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
151 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
152 153 

<h4>Firebird</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
154 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
155 156 157 
Firebird 1.5 (default installation) was tested, but the results are not published currently.
It is possible to run the performance test with the Firebird database,
and any information on how to configure Firebird for higher performance are welcome.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
158 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
159 160 

<h4>Why Oracle / MS SQL Server / DB2 are Not Listed</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
161 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
162 163 164 165 
The license of these databases does not allow to publish benchmark results.
This doesn't mean that they are fast. They are in fact quite slow,
and need a lot of memory. But you will need to test this yourself.
SQLite was not tested because the JDBC driver doesn't support transactions.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
166 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
167 168 169 170 

<h3>About this Benchmark</h3>

<h4>Number of Connections</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
171 
<p>
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
172 
This is mostly a single-connection benchmark.
Thomas Mueller's avatar
--no commit message
ac3c906a
 
Thomas Mueller committed
173 
BenchB uses multiple connections; the other tests use one connection.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
174 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
175 176 

<h4>Real-World Tests</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
177 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
178 179 180 
Good benchmarks emulate real-world use cases. This benchmark includes 3 test cases:
A simple test case with one table and many small updates / deletes.
BenchA is similar to the TPC-A test, but single connection / single threaded (see also: www.tpc.org).
Thomas Mueller's avatar
--no commit message
927afe2d
 
Thomas Mueller committed
181 
BenchB is similar to the TPC-B test, using multiple connections (one thread per connection).
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
182 
BenchC is similar to the TPC-C test, but single connection / single threaded.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
183 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
184 185 

<h4>Comparing Embedded with Server Databases</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
186 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
187 188 189 190 
This is mainly a benchmark for embedded databases (where the application runs in the same
virtual machine than the database engine). However MySQL and PostgreSQL are not Java
databases and cannot be embedded into a Java application.
For the Java databases, both embedded and server modes are tested.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
191 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
192 193 

<h4>Test Platform</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
194 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
195 
This test is run on Windows XP with the virus scanner switched off.
Thomas Mueller's avatar
--no commit message
b09fd536
 
Thomas Mueller committed
196 
The VM used is Sun JDK 1.5.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
197 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
198 199 

<h4>Multiple Runs</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
200 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
201 202 203 
When a Java benchmark is run first, the code is not fully compiled and
therefore runs slower than when running multiple times. A benchmark
should always run the same test multiple times and ignore the first run(s).
Thomas Mueller's avatar
--no commit message
ac3c906a
 
Thomas Mueller committed
204 
This benchmark runs three times, but only the last run is measured.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
205 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
206 207 

<h4>Memory Usage</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
208 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
209 210 
It is not enough to measure the time taken, the memory usage is important as well.
Performance can be improved in databases by using a bigger in-memory cache,
Thomas Mueller's avatar
--no commit message
bccf4e46
 
Thomas Mueller committed
211 
but there is only a limited amount of memory available on the system.
Thomas Mueller's avatar
--no commit message
ac3c906a
 
Thomas Mueller committed
212 
HSQLDB tables are kept fully in memory by default; this benchmark
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
213 214 215 216 
uses 'disk based' tables for all databases.
Unfortunately, it is not so easy to calculate the memory usage of PostgreSQL
and MySQL, because they run in a different process than the test. This benchmark currently
does not print memory usage of those databases.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
217 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
218 219 

<h4>Delayed Operations</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
220 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
221 222 223 
Some databases delay some operations (for example flushing the buffers)
until after the benchmark is run. This benchmark waits between
each database tested, and each database runs in a different process (sequentially).
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
224 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
225 226 

<h4>Transaction Commit / Durability</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
227 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
228 229 230 231 232 233 234 235 
Durability means transaction committed to the database will not be lost.
Some databases (for example MySQL) try to enforce this by default by calling fsync() to flush the buffers, but
most hard drives don't actually flush all data. Calling fsync() slows down transaction commit a lot,
but doesn't always make data durable. When comparing the results, it is important to
think about the effect. Many database suggest to 'batch' operations when possible.
This benchmark switches off autocommit when loading the data, and calls commit after each 1000
inserts. However many applications need 'short' transactions at runtime (a commit after each update).
This benchmark commits after each update / delete in the simple benchmark, and after each
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
236 
business transaction in the other benchmarks. For databases that support delayed commits,
Thomas Mueller's avatar
--no commit message
9d0f0920
 
Thomas Mueller committed
237 
a delay of one second is used.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
238 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
239 240 

<h4>Using Prepared Statements</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
241 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
242 
Wherever possible, the test cases use prepared statements.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
243 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
244 245 

<h4>Currently Not Tested: Startup Time</h4>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
246 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
247 248 249 250 251 252 253 
The startup time of a database engine is important as well for embedded use.
This time is not measured currently.
Also, not tested is the time used to create a database and open an existing database.
Here, one (wrapper) connection is opened at the start,
and for each step a new connection is opened and then closed.
That means the Open/Close time listed is for opening a connection
if the database is already in use.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
254 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
255
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
256 257 
<br /><a name="poleposition_benchmark"></a>
<h2>PolePosition Benchmark</h2>
Thomas Mueller's avatar
--no commit message
9cf66529
 
Thomas Mueller committed
258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 
<p>
The PolePosition is an open source benchmark. The algorithms are all quite simple.
It was developed / sponsored by db4o.
</p>
<table border="1" class="bar">
<tr><th>Test Case</th><th>Unit</th><th>H2</th><th>HSQLDB</th><th>MySQL</th></tr>
<tr><td>Melbourne write</td><td>ms</td><td>369</td><td>249</td><td>2022</td></tr>
<tr><td>Melbourne read</td><td>ms</td><td>47</td><td>49</td><td>93</td></tr>
<tr><td>Melbourne read_hot</td><td>ms</td><td>24</td><td>43</td><td>95</td></tr>
<tr><td>Melbourne delete</td><td>ms</td><td>147</td><td>133</td><td>176</td></tr>
<tr><td>Sepang write</td><td>ms</td><td>965</td><td>1201</td><td>3213</td></tr>
<tr><td>Sepang read</td><td>ms</td><td>765</td><td>948</td><td>3455</td></tr>
<tr><td>Sepang read_hot</td><td>ms</td><td>789</td><td>859</td><td>3563</td></tr>
<tr><td>Sepang delete</td><td>ms</td><td>1384</td><td>1596</td><td>6214</td></tr>
<tr><td>Bahrain write</td><td>ms</td><td>1186</td><td>1387</td><td>6904</td></tr>
<tr><td>Bahrain query_indexed_string</td><td>ms</td><td>336</td><td>170</td><td>693</td></tr>
<tr><td>Bahrain query_string</td><td>ms</td><td>18064</td><td>39703</td><td>41243</td></tr>
<tr><td>Bahrain query_indexed_int</td><td>ms</td><td>104</td><td>134</td><td>678</td></tr>
<tr><td>Bahrain update</td><td>ms</td><td>191</td><td>87</td><td>159</td></tr>
<tr><td>Bahrain delete</td><td>ms</td><td>1215</td><td>729</td><td>6812</td></tr>
<tr><td>Imola retrieve</td><td>ms</td><td>198</td><td>194</td><td>4036</td></tr>
<tr><td>Barcelona write</td><td>ms</td><td>413</td><td>832</td><td>3191</td></tr>
<tr><td>Barcelona read</td><td>ms</td><td>119</td><td>160</td><td>1177</td></tr>
<tr><td>Barcelona query</td><td>ms</td><td>20</td><td>5169</td><td>101</td></tr>
<tr><td>Barcelona delete</td><td>ms</td><td>388</td><td>319</td><td>3287</td></tr>
<tr><td>Total</td><td>ms</td><td>26724</td><td>53962</td><td>87112</td></tr>
</table>
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
286 
<br /><a name="application_profiling"></a>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
287 288 
<h2>Application Profiling</h2>
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
289 
<h3>Analyze First</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
290 
<p>
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
291 
Before trying to optimize the performance, it is important to know where the time is actually spent.
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
292 293 
The same is true for memory problems.
Premature or 'blind' optimization should be avoided, as it is not an efficient way to solve the problem.
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
294 
There are various ways to analyze the application. In some situations it is possible to
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
295 
compare two implementations and use System.currentTimeMillis() to find out which one is faster.
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
296 
But this does not work for complex applications with many modules, and for memory problems.
Thomas Mueller's avatar
--no commit message
755bd88a
 
Thomas Mueller committed
297 298 
</p>
<p>
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
299 
A very good tool to measure both the memory and the CPU is the
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
300 301 
<a href="http://www.yourkit.com">YourKit Java Profiler</a>. This tool is also used
to optimize the performance and memory footprint of this database engine.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
302 
</p>
Thomas Mueller's avatar
--no commit message
755bd88a
 
Thomas Mueller committed
303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 
<p>
A simple way to profile an application is to use the built-in profiling tool of java. Example:
</p>
<pre>
java -Xrunhprof:cpu=samples,depth=16 com.acme.Test
</pre>
<p>
Unfortunately, it is only possible to profile the application from start to end.
</p>

<br /><a name="database_profiling"></a>
<h2>Database Profiling</h2>
<p>
The ConvertTraceFile tool generates SQL statement statistics at the end of the SQL script file.
The format used is similar to the profiling data generated when using java -Xrunhprof. 
As an example, execute the the following script using the H2 Console:
</p>
<pre>
SET TRACE_LEVEL_FILE 3;
DROP TABLE IF EXISTS TEST;
CREATE TABLE TEST(ID INT PRIMARY KEY, NAME VARCHAR(255));
@LOOP 1000 INSERT INTO TEST VALUES(?, ?);
SET TRACE_LEVEL_FILE 0;
</pre>
<p>
Now convert the .trace.db file using the ConvertTraceFile tool:
</p>
<pre>
java -cp h2.jar org.h2.tools.ConvertTraceFile 
  -traceFile "~/test.trace.db" -script "~/test.sql"
</pre>
<p>
The generated file <code>test.sql</code> will contain the SQL statements as well as the
following profiling data (results vary):
</p>
<pre>
-----------------------------------------
-- SQL Statement Statistics
-- time: total time in milliseconds (accumulated)
-- count: how many times the statement ran
-- result: total update count or row count
-----------------------------------------
-- self accu    time   count  result sql
--  62%  62%     158    1000    1000 INSERT INTO TEST VALUES(?, ?);
--  37% 100%      93       1       0 CREATE TABLE TEST(ID INT PRIMARY KEY, NAME VARCHAR(255));
--   0% 100%       0       1       0 DROP TABLE IF EXISTS TEST;
--   0% 100%       0       1       0 SET TRACE_LEVEL_FILE 3;
</pre>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
351
Thomas Mueller's avatar
--no commit message
b492f851
 
Thomas Mueller committed
352 
<br /><a name="database_performance_tuning"></a>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
353 354 355 
<h2>Database Performance Tuning</h2>

<h3>Virus Scanners</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
356 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
357 358 359 360 361 362 
Some virus scanners scan files every time they are accessed.
It is very important for performance that database files are not scanned for viruses.
The database engine does never interprets the data stored in the files as programs,
that means even if somebody would store a virus in a database file, this would
be harmless (when the virus does not run, it cannot spread).
Some virus scanners allow excluding file endings. Make sure files ending with .db are not scanned.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
363 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
364 365 

<h3>Using the Trace Options</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
366 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
367 
If the main performance hot spots are in the database engine, in many cases the performance
Thomas Mueller's avatar
--no commit message
95620da6
 
Thomas Mueller committed
368 
can be optimized by creating additional indexes, or changing the schema. Sometimes the
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
369 370 371 
application does not directly generate the SQL statements, for example if an O/R mapping tool
is used. To view the SQL statements and JDBC API calls, you can use the trace options.
For more information, see <a href="features.html#trace_options">Using the Trace Options</a>.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
372 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
373 374 

<h3>Index Usage</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
375 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
376 377 378 379 380 381 382 383 
This database uses indexes to improve the performance of SELECT, UPDATE and DELETE statements.
If a column is used in the WHERE clause of a query, and if an index exists on this column,
then the index can be used. Multi-column indexes are used if all or the first columns of the index are used.
Both equality lookup and range scans are supported.
Indexes are not used to order result sets: The results are sorted in memory if required.
Indexes are created automatically for primary key and unique constraints.
Indexes are also created for foreign key constraints, if required.
For other columns, indexes need to be created manually using the CREATE INDEX statement.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
384 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
385 386 

<h3>Optimizer</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
387 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
388 389 390 391 392 393 
This database uses a cost based optimizer. For simple and queries and queries with medium complexity
(less than 7 tables in the join), the expected cost (running time) of all possible plans is calculated,
and the plan with the lowest cost is used. For more complex queries, the algorithm first tries
all possible combinations for the first few tables, and the remaining tables added using a greedy algorithm
(this works well for most joins). Afterwards a genetic algorithm is used to test at most 2000 distinct plans.
Only left-deep plans are evaluated.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
394 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
395 396 

<h3>Expression Optimization</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
397 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
398 399 400 401 
After the statement is parsed, all expressions are simplified automatically if possible. Operations
are evaluated only once if all parameters are constant. Functions are also optimized, but only
if the function is constant (always returns the same result for the same parameter values).
If the WHERE clause is always false, then the table is not accessed at all.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
402 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
403 404 

<h3>COUNT(*) Optimization</h3>
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
405 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
406 407 408 
If the query only counts all rows of a table, then the data is not accessed.
However, this is only possible if no WHERE clause is used, that means it only works for
queries of the form SELECT COUNT(*) FROM table.
Thomas Mueller's avatar
--no commit message
81c34acc
 
Thomas Mueller committed
409 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
410 411 

<h3>Updating Optimizer Statistics / Column Selectivity</h3>
Thomas Mueller's avatar
--no commit message
2ceb8a1f
 
Thomas Mueller committed
412 
<p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
413 414 415 416 
When executing a query, at most one index per joined table can be used.
If the same table is joined multiple times, for each join only one index is used.
Example: for the query SELECT * FROM TEST T1, TEST T2 WHERE T1.NAME='A' AND T2.ID=T1.ID,
two index can be used, in this case the index on NAME for T1 and the index on ID for T2.
Thomas Mueller's avatar
--no commit message
2ceb8a1f
 
Thomas Mueller committed
417 
</p><p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
418 419 420 421 422 423 424 425 
If a table has multiple indexes, sometimes more than one index could be used.
Example: if there is a table TEST(ID, NAME, FIRSTNAME) and an index on each column,
then two indexes could be used for the query SELECT * FROM TEST WHERE NAME='A' AND FIRSTNAME='B',
the index on NAME or the index on FIRSTNAME. It is not possible to use both indexes at the same time.
Which index is used depends on the selectivity of the column. The selectivity describes the 'uniqueness' of
values in a column. A selectivity of 100 means each value appears only once, and a selectivity of 1 means
the same value appears in many or most rows. For the query above, the index on NAME should be used
if the table contains more distinct names than first names.
Thomas Mueller's avatar
--no commit message
2ceb8a1f
 
Thomas Mueller committed
426 
</p><p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
427 428 
The SQL statement ANALYZE can be used to automatically estimate the selectivity of the columns in the tables.
This command should be run from time to time to improve the query plans generated by the optimizer.
Thomas Mueller's avatar
--no commit message
2ceb8a1f
 
Thomas Mueller committed
429 
</p>
Thomas Mueller's avatar
--no commit message
23c4f01c
 
Thomas Mueller committed
430
Thomas Mueller's avatar
javadocs
528531e5
 
Thomas Mueller committed
431 432 433 434 435 436 
<h3>Optimization Examples</h3>
<p>
See <code>src/test/org/h2/samples/optimizations.sql</code> for a few examples of queries 
that benefit from special optimizations built into the database. 
</p>
Thomas Mueller's avatar
The documentation no longer uses a frameset (except the Javadocs).
20d71e3b
 
Thomas Mueller committed
437 
<!-- [close] { --></div></td></tr></table><!-- } --><!-- analytics --></body></html>