You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: bart[at]vanhauwaert.org [Added to the original trac issue at 11.42am, Monday, 24th March 2008]
There is a caching mechanism in place, but it seems not effective for the expanded list of features. What we probably should do is for each feature keep a (cached) list of all possible painters and only try to match within that list. It trades memory for speed, however.
Reporter: koying
[Submitted to the original trac issue database at 6.12am, Sunday, 23rd March 2008]
On my machine, using the "Mapnik" style shows a steep loss of painting performance, probably due to the increased number of tags pairs specified.
Running a valgrind shows that much time is spend in FeaturePainter::matchesTag.
Could the process be tuned?
The text was updated successfully, but these errors were encountered: