mapbox / mapbox/mapbox-navigation-android
Move ReplayRouteMapper interaction to a worker thread
Open
Nobody has claimed this yet.
jira-sync-complete
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
The `ReplayRouteMapper` can take a significant amount of time parsing geometries when leg switches or when the simulation is started, we should look into options of moving the processing out of the main thread.
/cc @kmadsen @Guardiola31337
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating ReplayRouteMapper and tracing geometry parsing during leg switches and simulation startup. Profile the work on the main thread and determine whether it can run on a worker thread without changing replay behavior; done means the processing no longer blocks the main thread and the affected flows remain correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100