Hi Thierry, Onil,
First let me iterate what I wrote last week, the OSM stuff in Roassal is very cool, very
well written. Great work.
Since I have some experience with OSM maps, tiles and serving them, I had a look to see if
I could optimise the tile drawing/loading, which is visibly a bit slow, one would assume
because of the loading of the tiles over the network.
I just committed (based on code that I wrote some time ago):
Time: 28 January 2015, 2:31:50.462461 pm
Introduction of TROSMTileProvider to optimize getting OSM tiles, adds one shared memory
cache and a local file system cache, predefines and reuses 6 http clients spread over
Modifies TROSMShape>>#getTile: and adds TROSMShape>>#tileNamed:
The strange thing is though, that I can optimise the loading (as benchmarked separately),
but in most cases (not when they are in the memory cache, but when they are in the file
cache) the drawing still has the same pauses as before - which I don't understand, at
all. But it is a bit hard to explain.
Anyway, Thierry, I will see you tomorrow and the day thereafter and I hope I can show you
what I mean.
Show replies by date