Keep graph in Ram
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- cpp, postgresql
- 领域
- databases, performance
调研方向
The issue describes caching graph data in memory to avoid repeated database loads. Look at the pgRouting source code to understand how graphs are currently loaded from PostgreSQL and built into Boost C++ structures. Investigate the existing algorithm entry points and data structures to see where a caching layer could be inserted. Determine the memory footprint of typical graphs and design a cache lifecycle that works within the extension's architecture.
由索引模型根据 Issue 内容生成。
描述
To optimize performance for large graphs, I have some ideas that could potentially improve the process. Currently, with every call to pgRouting, there is a time overhead for loading the graph from the PostgreSQL database and building the Boost C++ graph structure internally before running the algorithm.
My idea is to explore two possible approaches:
Keep the Graph in RAM:
It is possible to load the entire graph from the PostgreSQL database into RAM and keep it there during the lifetime of the application or API. By doing so, subsequent calls to the routing algorithm can directly access the graph data in memory, significantly reducing the overhead of loading the graph from the database each time.
Generate Boost Graph Structure in RAM:
If keeping the entire graph in RAM is not feasible due to size constraints, another approach is to generate the Boost C++ graph structure directly in memory and cache it for subsequent algorithm calls.
- 主要语言
- C++
- 星标
- 1.4k
- 派生
- 397
- 平均合并
- 2 天 2 小时
- 30 天内合并 PR
- 4
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pgRouting/pgrouting 的其他 Issue
-
Boost broken links可能已有人在做 @Nandan-Raichura-Dev 于 1 天前认领。 未关闭Enhancement
难度 2/5 1-3 小时 新手友好度 68/100
pgRouting/pgrouting#3176 · 1 条评论 ·
维护者通常 2 天内回复
-
Administrative Enhancement
难度 1/5 1 小时以内 新手友好度 80/100
维护者通常 2 天内回复
-
points_input Developers doc可能已有人在做 @withaman69 于 85 天前认领。 未关闭C/C++ Developers Doc. good first issue
难度 2/5 1-3 小时 新手友好度 70/100
pgRouting/pgrouting#973 · 10 条评论 ·
维护者通常 2 天内回复
-
get_check_data developers doc可能已有人在做 @withaman69 于 87 天前认领。 未关闭C/C++ Developers Doc. good first issue
难度 2/5 1-3 小时 新手友好度 70/100
pgRouting/pgrouting#972 · 7 条评论 ·
维护者通常 2 天内回复
-
circuits Functionality Request
难度 5/5 一周以上 新手友好度 35/100
维护者通常 2 天内回复
查看 pgRouting/pgrouting 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
ROCm/FastFlowLM#887 ·
维护者通常 1 天内回复
-
paraview 6.2.0 uses Abseil 20260526 symbols but does not pin libabseil (undefined symbol with libabseil 20260817)可能已有人在做 @jschueller 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 64/100
-
bug medium priority openmp tokenizer wrong result
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 92/100
apache/casbin-cpp#277 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
iamaisim/ProjectAirSim#241 ·
维护者通常 1 天内回复