Opened 9 years ago

Closed 9 years ago

#2441 closed enhancement (wontfix)

MaxTilesetComplexity is not adequate enough to limit big jobs

Reported by: woidrick Owned by: osm@…
Priority: minor Milestone: Wishlist
Component: tilesathome Version:
Keywords: MaxTilesetComplexity, maplint Cc:

Description

I understand MaxTilesetComlexity? as a how large in megabytes generated tileset will be. The amount of RAM used for rendering is more adequate parameter.

Example: 1025 1694 12 is about 4000000 comlexity but when maplint layer rendered, it eats more than 20Gb RAM because of many errors notifications rendered for this tileset

May be it is not easy to calculate amount of RAM used, but the size of svg file used for rendering by inkscape can be checked before running inkscape.

So, additional complexity limit variable should be used.

Or when rendering of many simmillar writings shoud be rendered in less resource eating matter.

Change History (1)

comment:1 Changed 9 years ago by spaetz

Milestone: Wishlist
Priority: majorminor
Resolution: wontfix
Status: newclosed

The size of the svg and the size of the png files correlate pretty well, so there is little value in checking the size of the .svg value. In addition the server never sees the .svg files so the clients would have to transfer that information and the server would have to store that information in some data base (there is no database for each tileset file now and the tileset file size is easily to get at.

So this is a won'tfix from the server side. I agree that the RAM usage by inkscape would be the best measurement but that is information that the client cannot get at.

It used to be that the regular tilesets and maplint RAM usage deviated a lot. That has become a lot better with the maplint layer gone now.

Note: See TracTickets for help on using tickets.