On the DEC Alpha, the commit times do not behave as expected. The commit
time per object seems to be dependent of how many objects have already
been loaded into the database. The table below shows different strategies
to commit: first, commit after a certain number of objects. The commit
time
changes from 5.5 to 3 hours. The second strategy is to restart the
program after 30000 or 50000 objects, continuing the loading where it left
off.
This shows the expected behaviour: no dependence on the number of objects
already loaded can build up.
|
|
|
|
|
|
|
3000
|
8:17:53
|
1:58:24
|
5:33:43
|
0:45:46
|
|
6000
|
6:53:49
|
2:02:53
|
4:09:57
|
0:40:59
|
|
10000
|
6:21:12
|
1:58:24
|
3:45:35
|
0:37:13
|
|
20000
|
5:52:11
|
2:02:17
|
3:11:27
|
0:38:27
|
|
50000
|
6:51:46
|
1:57:37
|
4:16:45
|
0:37:24
|
| 10000, restart after 30000 |
3:19:18
|
2:04:06
|
0:37:03
|
0:38:09
|
| 10000, restart after 50000 |
3:37:39
|
2:06:39
|
0:49:46
|
0:41:14
|
The commit times while loading are displayed below. See the comparison
to SGI for more details.