Skip to content

⚡ Optimize SQLiteSpanExporter batch insertions#116

Open
eterna2 wants to merge 1 commit into
mainfrom
perf/sqlite-span-exporter-39712440089232414
Open

⚡ Optimize SQLiteSpanExporter batch insertions#116
eterna2 wants to merge 1 commit into
mainfrom
perf/sqlite-span-exporter-39712440089232414

Conversation

@eterna2

@eterna2 eterna2 commented Jul 14, 2026

Copy link
Copy Markdown
Owner

💡 What: Replaced the loop executing single INSERT OR REPLACE statements in SQLiteSpanExporter.export with a single conn.executemany statement using a generator expression.
🎯 Why: To resolve an N+1 query issue. SQLite has to compile and execute each statement separately in a loop, whereas executemany allows executing multiple sets of parameters against a single prepared statement, lowering CPU load and overhead.
📊 Measured Improvement: In a benchmark testing the insertion of 100,000 mock spans into a file-based temporary SQLite database:

  • Baseline: ~1.09 seconds.
  • Optimized: ~0.81 seconds.
  • Improvement: ~25.7% speedup over baseline.

PR created automatically by Jules for task 39712440089232414 started by @eterna2

💡 What: Replaced the loop executing single INSERT OR REPLACE statements in SQLiteSpanExporter.export with a single conn.executemany statement using a generator expression.
🎯 Why: To resolve an N+1 query issue. SQLite has to compile and execute each statement separately in a loop, whereas executemany allows executing multiple sets of parameters against a single prepared statement, lowering CPU load and overhead.
📊 Measured Improvement: In a benchmark testing the insertion of 100,000 mock spans into a file-based temporary SQLite database:
  - Baseline: ~1.09 seconds.
  - Optimized: ~0.81 seconds.
  - Improvement: ~25.7% speedup over baseline.

Co-authored-by: eterna2 <1248825+eterna2@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.

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.

1 participant