[Tilesathome] Using RAM-drive for ROMA temp tables
Mathieu Arnold
mat at mat.cc
Sat Dec 6 08:22:58 GMT 2008
+--On 6 décembre 2008 08:46:24 +0100 Florian Lohoff <flo at rfc822.org> wrote:
| My guess is that the only solution is ram, ram and more ram. The problem
| with the node index is basically that the width is very small and thus
| the index is nearly as large as the table itself - IIRC its about
| 11-12GByte. So when you have less memory than that every access is going
| to hit disk very early - namely trying to get nodes in a bbox via the
| gist index. My guess would be that you'll see good performance gain up to
| 10-20GByte memory and then once you have the full database in memory but
| thats out of the scope of most of us.
I'd like to add one thing at that. On my instance, the query returning the
nodes in the bbox takes at most 1s, and most of the time is under 0.1s. The
index takes about 14GB, and I only have 3.5GB of RAM. I do think it's *not*
that bad :-)
--
Mathieu Arnold
More information about the Tilesathome
mailing list