mapping - Temporary tiles cache for Mapserver -

i searching on google , stackoverflow see if have solution problem, didn't found same problems.

so, i'm running debian machine mapserver installed on it. server run webserver displaying map data on browser. generation of map dynamic, based on layers definition in database built mapfile in php , based on generated php map shown user. data defined in database , shp files (both combined in single mapfile).

it dynamic, mean user can enable/disable of layers or click inside polygon (select points on map) color selection (generate new mapfile based on selection , re-generate tiles).

so execution of code selecting area coloring selected items somtimes take time user experience.

for solution i'd use kind of temporary tiles cache, can used single user, , able delete it's content when user select items on map or enable/disable 1 of layers.

p.s. did optimizations provided mapserver documentation.

thanks help.

it sounds me problem not going helped server-side caching. if of tiles depend on user selections, you're going generating bunch of new tiles every time there's interaction.

i've been using mapcache solve similar problem, rendering tileset in response user query. i've broken tiles multiple logical layers, , compositing on browser side. lets me cache, server-side, tiles various queries, , sped performance immensely. did seed cache down zoom level 12, , needed use berkeleydb cache type keep running out of inodes.

i'm using leaflet.js browser-side rendering, should consider openlayers.

---

after looking @ source code, have other ideas.

it looks you're drawing each layer same way each time. right? is, style , predicate of particular layer never change. each user sees image layer same way, if have selected layer. combination of layers show change, based on openlayers control? if that's case, don't need per-user caching on server. instead, use per-layer caching, , let user's browser figure out client side caching.

a quick technique finding slow layers turn them of. reenable them 1 one find culprit. invoke mapserver command line, , time runs, greater precision you'll running webserver.

you mentioned you're serving images in google 3857 while layers in gauss-kruger/epsg 3912. reprojecting on fly expensive. reprojecting rasters on fly expensive. if can, should reproject them ahead of time, , store them in 3857 (add additional geometry column).

i don't know dof file is--maybe digital obstacle file? perhaps preload dof file postgis too? eliminate 2 pieces think problematic.

take @ sql queries postgis performing, , make sure using indexes

in case, these individual layers should go mapcache, in opinion. here video of september 2014 talk mapcache project leader.