Skip to content
ParticleDB

Improve query performance

Use representative record counts, value distributions, filters and concurrency. Record server version, hardware and configuration. Compare results before comparing timings.

Select the columns you need. Add selective filters and use a suitable index when the release supports it. Large offsets, wide records and high-cardinality grouping can change the cost substantially.

EXPLAIN SELECT id, title FROM work_items WHERE id = 1;

This uses the sample table from relational data. A plan is a diagnostic, not a latency promise. Use supported profiling tools to identify expensive work.

Compare individual writes with bounded batches. Preserve the same transaction and durability settings in both runs. Keep retries and memory use in the measurement.

Documentation examples establish behavior. Benchmark results require a complete workload, configuration and repeated measurements. See benchmark methodology.

Documentation home · Troubleshooting