Hello....
I'm using the Magick Wand C API in a custom map tileserver. The
tileserver consumes an overly excessive amount of memory during tile
generation, which has lead me to some questions about how ImageMagick
deals with virtual pixels internally.
Most image generations are limited to 256x256 px. It's a threaded
design (one thread per connection), so I'm using semaphores to limit the
number of concurrent image generations to 10. Following the
architecture document, the maximum memory that should be consumed by the
Image Magick pixel cache would then be (using the Q16 version):
256 x 256 x 2 x 5 x 10 = 6,553,600 bytes
Now here is the question. Often times in drawing these images, I end up
drawing polygons that are very large, and only a small part of them is
actually contained inside the "authentic pixel" area of the image. To
put it another way, much of the polygon can be drawn way outside of the
256 x 256 area. My question is: When doing so, does the pixel cache
expand to accommodate the "virtual" area? Is is possible that this is
where the large memory consumption is happening ?
Thanks In Advance,
Larry
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
