Skip to content

fix: bolt optimization for full graph exports peak memory overhead - #1015

Merged
n24q02m merged 1 commit into
mainfrom
bolt-optimize-export-memory-10172509774891061715
Sep 10, 2026
Merged

fix: bolt optimization for full graph exports peak memory overhead#1015
n24q02m merged 1 commit into
mainfrom
bolt-optimize-export-memory-10172509774891061715

Conversation

@n24q02m

@n24q02m n24q02m commented Sep 6, 2026

Copy link
Copy Markdown
Owner

💡 What: Optimized full graph exports (export_graphml, export_jsonld, export_dot, export_cypher, and export_crg) to stream directly from sqlite3.Cursor rows via new GraphStore.iter_raw_nodes() and GraphStore.iter_raw_edges() methods, instead of loading the entire graph into Python GraphNode/GraphEdge objects.

🎯 Why: Previously, generating exports required materializing tens of thousands of dataclass instances in memory, leading to massive peak memory spikes and CPU overhead during object construction, which is unnecessary since export formats only require scalar row values.

📊 Impact: Significantly reduces peak memory utilization and CPU time during full graph exports (O(1) python object overhead instead of O(N)).

🔬 Measurement: Memory profiling a call to export_crg against a large repository will show substantially lower peak memory overhead as GraphNode and GraphEdge object instantiations are completely eliminated during the export loop.


PR created automatically by Jules for task 10172509774891061715 started by @n24q02m

Co-authored-by: n24q02m <135627235+n24q02m@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions github-actions Bot added the bot-generated Automatically created by a bot tool (Jules, Bolt, Palette, etc.) label Sep 6, 2026
@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@n24q02m
n24q02m merged commit 6ed06b0 into main Sep 10, 2026
21 checks passed
@n24q02m
n24q02m deleted the bolt-optimize-export-memory-10172509774891061715 branch September 10, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot-generated Automatically created by a bot tool (Jules, Bolt, Palette, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant