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?
On Tue, Jan 4, 2011 at 10:48 AM, Tom Hughes <[email protected]> wrote: > On 04/01/11 08:20, Frans Hals wrote: > >> My experiences with Amazon and Nominatim had been horrible, didn't matter >> which instance I took. >> Just a big waste of time/money. Switched to a dedicated server for much less >> the price... > > EC2 is generally known to not perform well for any task where disk I/O > is an important factor. > > Tom > > -- > Tom Hughes ([email protected]) > http://compton.nu/ > _______________________________________________ Geocoding mailing list [email protected] http://lists.openstreetmap.org/listinfo/geocoding
