[Tilecache] calculate used memory for tilecache_seed

[2StepForward]

2StepForward wrote:
> 
> Hi all,
> 
> I have a problem with an exception by execute of tilecache_seed.
> Exception is: 
> 2008-04-17 13:16:02,121 ERROR [coverage.processing] - Tile cache capacity
> exceed maximum heap size (1.290 Mb).
> 
> First I think is wow :-0, it used a lot of memory. I've give him per
> wrapper.conf 1,3 Gb memory.
> 
> I use a image as coverage in GeoServer with size of 11178 x 14790
> and a extend of  bbox=259828, 5230501, 920728, 6084502
> 
> Here the tilecache.cfg:
> 
> [D1M]
> type=WMSLayer
> url=http://ip/geoserver/wms?
> size=1024,1024
> layers=WCS:Deutschland_1Mio.0
> extension=png
> bbox=259828, 5230501, 920728, 6084502
> srs=EPSG:23032
> levels=4
> resolutions=57.74, 28.87, 14.43, 7.21
> 
> Resolutions was calculated by 6084502 - 5230501 / 14790 = 57.74 meter per
> pixel by a scale of 1:1Mio
> Now it will produce several pieces in 1024 x 1024 with 57.74 meter per
> pixel...... and so on all resolutions down. 
> I will take the 1:1 presenting with scale 1:1Mio as first Zoomlevel
> (zoomlevel==0) tiled in pieces of 1024 X 1024.
> 
> But it fails secounds after I started the tilecache_seed with an out of
> memory exception.....
> 
> Knows anybody why.
> If I calculate the memory than I will get:
> 
> - The picture is in 4 bpp.
> 
> 11178 x 14790 = 165322620 bytes in 32 bit mode (*8) = (1322580960 / 1024)
> / 1024 = 1261,311 mb
> 
> It is realy big for working in RAM but I have no choice. I think the given
> memory is enough, but my server say no......
> 
> Last question, can anybody explain how the algorithm, or whole image
> producing process (abstract) work's. I don't understand how work's the
> image producing process in the memory.
> 
> Sorry for some editing......
> 
> Has anybody a idea......,
> Realy thanks Klaus
> 

-- 
View this message in context: http://www.nabble.com/calculate-used-memory-for-tilecache_seed-tp16743543p16743994.html
Sent from the TileCache mailing list archive at Nabble.com.