ensindexer-perf-testing

To run reproducible performance tests for an ENSIndexer instance, this Skill automates end-to-end baselining and per-handler timing collection across local Postgres and ENSRainbow environments. It orchestrates prerequisite setup like Prometheus and Grafana to ensure controlled, apples-to-apples comparisons.

Before baseline testing ENSIndexer with Postgres, you need a clean working tree, Docker daemon running, and Postgres at postgresql://postgres@localhost:5432/ponder. ENSRainbow must be hydrated and the DISABLE_ENSRAINBOW_HEAL environment variable set for baseline runs.

Yes, you can compare ENSIndexer branches, configurations, and plugin combinations under controlled conditions. The workflow orchestrates clean state initialization and deterministic baselining to capture wall-clock and per-handler timings for repeatable results.

Grafana and Prometheus integration works with ENSIndexer perf testing by orchestrating their initialization as part of the guided setup workflow. This captures baseline performance metrics and wall-clock timings during the indexer run for visual monitoring and analysis.

Inconsistent ENSIndexer performance baseline comparisons often occur when prerequisite setup is incomplete. Ensure you have a clean working tree, hydrated ENSRainbow data, and the DISABLE_ENSRAINBOW_HEAL environment variable set to produce deterministic, apples-to-apples results.