indexing-performance

Tunes HyperSync, batch sizes, and RPC parameters to optimize indexer throughput and stability for historical/live indexing workflows.

2|3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-performance-moose-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: indexing-performance
Source: https://github.com/moose-code/polymarket-indexer/tree/main/.claude/skills/indexing-performance
Command: npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-performance-moose-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Optimizes Polymarket's indexer throughput and stability by tuning HyperSync, batch sizes, and RPC parameters.

Core Features & Use Cases

  • HyperSync as default data source for historical and live indexing, delivering maximum speed with automatic configuration.
  • Batch size tuning to balance throughput and resource usage.
  • RPC tuning options to trade latency and reliability per chain.
  • WebSocket-based live indexing hints to reduce latency in new block detection.
  • Database index guidance to speed up common queries and data retrieval.

Quick Start

Tune the indexer by adjusting batch size and RPC settings to optimize throughput on your deployment.

Frequently Asked Questions about indexing-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I tune indexer throughput for faster historical syncing?

Tune indexer throughput by adjusting batch sizes and RPC parameters to balance resource usage during historical synchronization. HyperSync serves as the default data source, delivering maximum speed with automatic configuration for faster syncing.

What is the best way to reduce latency during live blockchain indexing?

Reduce latency during live indexing by enabling WebSocket-based hints for new block detection and applying chain-specific RPC tuning. These settings trade latency for reliability, optimizing real-time data retrieval stability.

Does HyperSync work for both historical synchronization and live indexing?

HyperSync works as the default data source for both historical synchronization and live indexing. It delivers maximum syncing speed through automatic configuration, while RPC parameters can be further tuned per chain.

How do I balance batch size and resource usage when indexing blockchain data?

Balance batch size and resource usage by tuning batch parameters according to your deployment capacity. Larger batches increase indexer throughput but consume more resources, requiring careful tuning based on chain-specific defaults and safety guidance.

Why is my indexer syncing slowly and how can database indexing help?

Slow syncing can result from unoptimized database queries. Applying database index guidance speeds up common queries and data retrieval, complementing HyperSync and batch size tuning to improve overall indexer throughput.