D Tucny skrev: > The ability for the [EMAIL PROTECTED] client to use only background resources > needs to be > a higher priority than quick throughput... The fact that it couldn't be > trusted to not affect other services is why I had to remove it from the > machines I was running it on, thought admittedly, the issue there wasn't CPU > usage but memory usage where even with 4+GB of RAM the combination of other > services using RAM and the occasional very complex tile causing massive > memory usage caused the machine and all services running on it to grind to a > near halt for a while... If I get time to look at it again, I'll probably > look at finding a way to limit RAM usage, but, this is just an example in > this context of issues that can cause [EMAIL PROTECTED] to interfere with the > running of > other system services that could also be triggered by certain parts of > [EMAIL PROTECTED] at higher priorities which is my only concern here... >
MaxTilesetComplexity = xxxxxxx in tilesAtHome.conf is what you are looking for. Just set it sufficiently low, and the client will automagically put complex tilerequests back to the queue and get another one. Dutch _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
