On Tue, Jan 04, 2011 at 06:23:48PM +0200, Teemu Ikonen wrote: > > There seems to be something else going on, the indexing in this case > is not I/O bound, at least what I can tell from the iostat / top > output, but CPU bound. And now it's getting slower and slower, 8 hours > ago it was churning 400MB/h, now its only 330MB/h and slowing down. > postgress process is still running at 100% cpu utilization. Maybe > amazon instance somehow scales down the CPU speed after a while? >
I have seen stuff like that on other OSM related imports and my explanation was that when you start indexing your index is empty. Your index grows with the amount of data you already indexed so your working set grows and thus your working speed decreases. Flo -- Florian Lohoff [email protected] Professionell gesehen bin ich zu haben ....
signature.asc
Description: Digital signature
_______________________________________________ Geocoding mailing list [email protected] http://lists.openstreetmap.org/listinfo/geocoding
