Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
use a pool of images to reduce re-allocation overhead #50
For export jobs that attempt to maximize machine resources in order to render a tile cache as fast as possible, the allocation and cleanup of mapnik.Image objects shows up in profiling traces. While image allocation seems like it should be of trivial cost compared to data access and rendering, the sheer number of images allocated (per metatile) + the nature of v8 garbage deferred collection means that we may be able to speed up renders by pooling images and re-using them.
Issues to tackle:
referenced this issue
Nov 12, 2012
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
Have you ever seen any rendering errors in the logs with runs that did not hang? I presume not, but I found and fixed this bug that would foreseeably cause a hang if a rendering error happened and the pool was not released.
I have progress on code to test the other todo's and then returning to try to reduce the test I think would be a solid plan.
mapnik/mapnik#1571 is done, which sets me up for exposing