Here's my figures when running a typical SELECT (see first post).
Flushed disk caches before (see http://linux-mm.org/Drop_Caches),
shows I/O bottleneck:
avg-cpu: %user %nice %system %iowait %steal %idle
6,40 0,00 2,46 41,87 0,00 49,26
Device: tps MB_read/s MB_wrtn/s MB_read MB_wrtn
sdb 227,00 19,64 0,88 19 0
Running the query again (when the 1,5gb table is cached by os) shows
user cpu bottleneck:
avg-cpu: %user %nice %system %iowait %steal %idle
45,77 0,00 10,95 0,00 0,00 43,28
Device: tps MB_read/s MB_wrtn/s MB_read MB_wrtn
sdb 0,00 0,00 0,00 0 0
So I'd say, depending on how much memory you have, large tables can
have big I/O bottlenecks.
What do you think?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en
-~----------~----~----~----~------~----~------~--~---
