Hi Pavithran, thanks for your answer.
Am 09.11.2012 um 03:04 schrieb pavithran <[email protected]>: > I understand you have set out the timeout configs but why is 17 or 18 > level tile not getting rendered on the fly ? Is it because of a very > slow hardware or dense location ( which is obvious due to map quality > in germany) . But I think its the postgres which is slowing you down . > Try keeping the postgres on a different machine if possible . The hardware is not too bad. AMD Athlon II X4 (Quad Core), 2,3GHz, 8 GB RAM, 2x1TB SATA II (Software-RAID1, but only 5.400rpm). Dedicated, not virtual. Unfortunately putting postgres on a different machine is not an option at this time due to budget restrictions. > Also regarding your choice of mod_tile , mod_tile is a meta tile > caching mechanism where the meta tile (8x8) is rendered . mod_tile is > good for prerendering and also serving large postion of tiles helpful > in panning , but the first request for a new tile in new location is > going to take time . :( For me it's ok that the first request takes some time. What I am only wondering about is that the metatile seems to be rendered in 3 seconds (Syslog: "Nov 8 20:23:55 xxxxxx renderd[16476]: DEBUG: DONE TILE default 17 69448-69455 43336-43343 in 2.967 seconds") - which would be ok for me for the first request - but the server answers with an 404 in 29-49ms. I would like the server to answer in these 3 seconds, but with the tiles and HTTP 200 and not with an 404. I tried several settings, such as ModTileRequestTimeout 500 ModTileMissingRequestTimeout 500 ModTileMaxLoadMissing 50 but still the same 404. Is there a possibility for find out why mod_tile return a 404, which timeout it runs into? Greetings, Stefan _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
