Our nominatim service at: http://nominatim.cyclestreets.net/
has been running since July. But according to the munin charts it seems to spend about half a day everyday thrashing the disk, and during that time the service is too slow for use in a production environment. Presumably this is doing a daily update? I've not yet tried the auto vacuuming suggestions following my previous query about the growth of the use of disk space - mainly because I'm not familiar with the workings of Postgres. It might help if I knew which commands to run in Postgres to vacuum the indexes and if that may also help with the thrashing problem? -- Simon Nuttall Route Master, CycleStreets.net _______________________________________________ Geocoding mailing list [email protected] https://lists.openstreetmap.org/listinfo/geocoding
