Tile loading performance

CS

Hi! I've noticed that 99% of the tiles load within a reasonable amount of time, but then there's just errant tiles that take quite a while (~6-10 seconds), or sometimes don't load. Naturally the tiles just happens to be where I'm looking often, of course. :) Just my vote for improving the UX here.

Here's some example errant tile load times that appear to just be software issues (as opposed to the network):

3

Comments

3 comments

Date Votes
  • Comment author
    Mark Egge

    I second this. Sometimes it seems like tile loading performance is pretty slow ... especially with a large window.

    0
  • Comment author
    caver456

    Upvote here.  This is probably ridiculously difficult to track down.  Looks like this particular report is referring to the web interface on a computer - in addition, it's always been an issue on Caltopo Desktop (CTD) and on the phone app even with locally stored tiles.  The continuous improvement definitely pays off with new releases of CTD over time, but it's still there.

    On the CTD side, we had assumed for a while that it was a latency on our IC trailer network (with Caltopo Desktop running on a different node on our trailer LAN) and have done a good bit of work trying to track down that mysterious LAN lag, but even running Caltopo Desktop on localhost, with the tiles stored on the laptop's SSD, the tile load issues like this remain.

    A few of us were also noting it on the phone app, on a few different phones yesterday, both of which did have the tiles already downloaded.  Maybe there was some interaction we just didn't understand with other layers or with map data hogging the phone CPU or such, but, the basemap tiles took several seconds to load up.  This was in an area with dodgy cell service.  The behavior we observed each time is that something was causing it to skip over the first few parts of the normal in the tile search sequence (cached then downloaded then internet).

    0
  • Comment author
    CS
    • Edited

    For sure these can be time consuming to resolve, and sometimes they can be completely unrelated to your code, but due to bugs in core libs and the JVM itself. It's really confusing since they're used so widely, but they really do have bugs in basic behavior that get fixed a decade later. Assuming the core issue isn't known, just upgrading all the deps to pick up all the bugs fixes would likely be the first naive step to try. My 2c from having had these types of issues  at scale in the past.

    0

Please sign in to leave a comment.