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

Optimise parsing process/calculation #7

Open
philipbelesky opened this issue Aug 18, 2021 · 0 comments
Open

Optimise parsing process/calculation #7

philipbelesky opened this issue Aug 18, 2021 · 0 comments
Labels
optimisation Making go fast

Comments

@philipbelesky
Copy link
Owner

From benchmarks, most of the work done in the component is in parsing through the XML file rather than in geometry creation. This is particularly noticeable in the Way component given it must traverse all Node and Way types. Options for improvement could include

  • For Way parsing: walk through the way nodes first, then route back to the nodes for faster checking if they are relevant
  • Multi-threading the walk through nodes
  • Micro-optimisations within the loop structures
  • Hybridising between the different processor approaches (e.g. Ling and XMLDoc) to use each for what it is fastest at
  • Skip duplication checks if only parsing a single XML file
  • Translating from latlon to XY with some sort of mass vector transformation
@philipbelesky philipbelesky added the optimisation Making go fast label Aug 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimisation Making go fast
Projects
None yet
Development

No branches or pull requests

1 participant