[Tilecache] Speedup things
Tyler Durden
tylersticky at gmail.com
Tue Oct 21 06:05:36 EDT 2008
Hi,
I'm using Postgres(8.2 with Postgis), TileCache(2.04) + Mapnik(0.5.1)
and tilecache_seed.py to generate the tiles.
The problem is that is slow(or think it is).
The machine has 2Gb RAM an Intel Quad Core 2.4.
In postgresql.conf:
shared_buffers = 128MB
work_mem = 32MB
effective_cache_size = 1024MB
Output from tilecache_seed.py:
...
03 (000435, 000310) = (7802492.0000 -197508.0000 7866492.0000
-133508.0000) [5.0868s : 4.386/s] 7900/15876
03 (000440, 000310) = (8122492.0000 -197508.0000 8186492.0000
-133508.0000) [5.1092s : 4.379/s] 7901/15876
03 (000445, 000310) = (8442492.0000 -197508.0000 8506492.0000
-133508.0000) [5.0622s : 4.372/s] 7902/15876
03 (000450, 000310) = (8762492.0000 -197508.0000 8826492.0000
-133508.0000) [4.6159s : 4.366/s] 7903/15876
03 (000455, 000310) = (9082492.0000 -197508.0000 9146492.0000
-133508.0000) [4.6226s : 4.360/s] 7904/15876
03 (000460, 000310) = (9402492.0000 -197508.0000 9466492.0000
-133508.0000) [4.6238s : 4.353/s] 7905/15876
03 (000465, 000310) = (9722492.0000 -197508.0000 9786492.0000
-133508.0000) [4.6130s : 4.347/s] 7906/15876
...
The streets layer has 900.000 rows. The rest of layers are between
10.000 and 80.000 rows.
I have created the indexes in the geometry fields and in the where(sql) fields.
Any tips to speedup things?
Thanks,
Tyler
More information about the Tilecache
mailing list