Changes between Initial Version and Version 1 of Ticket #20497, comment 5


Ignore:
Timestamp:
2021-02-19T11:20:41+01:00 (5 years ago)
Author:
GerdP

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20497, comment 5

    initial v1  
    1 So far I only found out that the large tile size also means more bytes for data that is downloaded but not visible. With 1024 instead of 512 the value is four times higher and thus it is more likely to hit the limit. The number of tiles in memory seems also to depend on the amount of view port changes (panning, zoom in/out).
     1So far I only found out that the large tile size also means more bytes for data that is downloaded but not visible. With 1024 instead of 512 the value is four times higher and thus it is more likely to hit the limit. The number of tiles in memory seems also to depend on the amount of view port changes (panning, zoom in/out) within a time period.
    22My assumption is that we have a situation where many tiles are downloaded for the first time and "waiting to be written to the disk cache" while more new tiles are downloaded. This alone seems to work well but maybe something goes wrong when network problems or other timeouts are involved. I wasn't able to reproduce the hang again so far, but I am still trying...