Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It seems that Vespucci caches also failed responses #726

Closed
matkoniecz opened this issue Jun 7, 2018 · 4 comments
Closed

It seems that Vespucci caches also failed responses #726

matkoniecz opened this issue Jun 7, 2018 · 4 comments

Comments

@matkoniecz
Copy link
Contributor

Vespucci Version

Vespucci 11.0.0-5

Download source

google play store

Device (Manufacturer and Model)

Xiaomi Redmi 4

Android Version

6.0.1

Behaviour/Symptoms

After period of poor connection and starting to receive good mobile internet tiles are not downloading.

After deleting cache tiles are downloading normally.

Expected Behaviour

Tile are downloading after restoring connection

How to recreate

Crash dump submitted (no or yes + date)

No

Any other potentially relevant information

It may be misinterpretation as flushing cache takes a long time

@matkoniecz matkoniecz changed the title It seems that Vespucci beeches also failed responses It seems that Vespucci caches also failed responses Jun 7, 2018
@simonpoole
Copy link
Collaborator

simonpoole commented Jun 7, 2018

Yes we do cache actual errors (aka that the tile doesn't exist, but iirc only for bing), but not network errors as far as possible. Essentially the tile in question simply gets removed from the queue once the downloader gives up, but depending on what is happening that may take a long time (as long as it is the queue it won't be retried, and in the typical very very slow network situation you might have lots of tile requests pending), Not sure if this is easily fixable.

Have you tried switching to a different layer and then back again? Other potential workaround: zooming in or out will remove all pending requests for other zoom levels (you do have zoom a full level though).

@simonpoole
Copy link
Collaborator

Do you see this particularly often with a specific layer?

FYI the (read) timeout is currently 5 seconds which assuming a tile size of 15-20kB should still be doable with a GPRS or GSM connection, you may need to lower the number of download threads from the standard of 4 down to 1 or 2 though. It is naturally clear that a tile per couple of seconds is very very slow (particularly because on current hi-res phones you may need a -lot- of tiles for the whole screen).

The -other- workaround for bad connectivity is to use a mbtiles container holding the tiles.

@matkoniecz
Copy link
Contributor Author

matkoniecz commented Jun 7, 2018

Do you see this particularly often with a specific layer?

Geoportal (imagery provided by Polish government) (though I use just this layer for 90%+ of time)

@simonpoole
Copy link
Collaborator

Closing, don't think there is anything currently actionable here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants