Skip to content

experimental: graphhopper upgrade fixes#116

Closed
MichaelsJP wants to merge 4 commits into
ors_4.0from
fix/graphhopper-upgrade-fixes
Closed

experimental: graphhopper upgrade fixes#116
MichaelsJP wants to merge 4 commits into
ors_4.0from
fix/graphhopper-upgrade-fixes

Conversation

@MichaelsJP

Copy link
Copy Markdown
Member

Please read our contributing guide and note that also your contribution falls under the Apache License 2.0 as outlined there.

Your first contribution should include a change where you add yourself to the CONTRIBUTORS.md file.

OSMNodeData stored barrier node tags in a List<Map<String,Object>>,
allocating a HashMap per tagged node. On a planet-scale import this
produces millions of short-lived hash maps, driving GC pause time and ballooning heap pressure throughout the read pass.

Backported KVStorage (com.graphhopper.search) to replace the list with a compact,
MMAP-backed byte store. Tags are serialised once and looked up by index,
eliminating per-node HashMap overhead entirely.

 When the fork is upgraded to a GH version that ships KVStorage natively, remove all
ORS-GH BACKPORT markers in OSMNodeData.java plus KVStorage.java and the
version constant.
@MichaelsJP MichaelsJP changed the title Fix/graphhopper upgrade fixes experimental: graphhopper upgrade fixes Jun 8, 2026
@aoles

aoles commented Jun 12, 2026

Copy link
Copy Markdown
Member

We have agreed to refrain from these changes for now, primarily because backporting of KVStorage doesn't seem to be critical.

@aoles aoles closed this Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants