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

Remove guidance data to reduce RAM usage? #5838

Open
jcoupey opened this issue Sep 23, 2020 · 4 comments
Open

Remove guidance data to reduce RAM usage? #5838

jcoupey opened this issue Sep 23, 2020 · 4 comments

Comments

@jcoupey
Copy link

jcoupey commented Sep 23, 2020

I'm usually not interested in route information apart from duration, distance and geometry, so I'm always using OSRM with steps=false. My understanding is that the matching data used to generate the steps array in response (RouteStep.name and RouteStep.ref values among others) is still loaded in RAM. Depending on the extract size, this may amount to a lot of unused data.

First of all, I'd like to figure whether trying not to load this data is worth the trouble. I can see osrm.names is not that big, but osrm.icd is. Is there a way to evaluate the potential gain here?

@SiarheiFedartsou
Copy link
Member

Done in #6045

@jcoupey
Copy link
Author

jcoupey commented Aug 28, 2022

#6045 is indeed related as it does save some calculation on route path data but as stated there: this PR is a first step towards making the loading of these datasets optional and making these changes unlocks the optional loading of data.

Optionally loading guidance data (or other parts of the data preprocessed by OSRM) is probably easier to implement now but it's still not possible.

Copy link

github-actions bot commented Jul 8, 2024

This issue seems to be stale. It will be closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Jul 8, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 9, 2024
@jcoupey
Copy link
Author

jcoupey commented Aug 9, 2024

While there has been no recent progress on this, I think it's worth keeping the ticket open as a feature request. It would be quite useful in many situations to be able to reduce memory requirements when some data is unused, and this would be easier to build now after #6666.

@jcoupey jcoupey reopened this Aug 9, 2024
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