RPC FAST · 11 SEPTEMBER 2026

Quark GPA latency

DeFi discovery

Quark vs Agave
QuarkAgave
RequestCommitmentQuarkAgaveRelative latencyResult itemsResponses / timeouts

Requests tested

Filtered getProgramAccounts calls that locate a specific pool or pair. Every result row names the lookup type and shows the exact account-size and byte-offset filters used for that protocol. The same filters and commitment were sent to Quark and Agave.

Full data

The regular base64 response: every matched public key, standard account metadata, and the complete account data bytes.

Keys only

The same filtered request with dataSlice: {offset: 0, length: 0}. It returns the matched public keys and account metadata while omitting the account data bytes.

Cold / first pass is the first observation in this run; caches were not cleared. Warm repeats combines the following three passes. A request without a complete response after 60 seconds is recorded as 60 s and the next request starts immediately.

“≥ 60 s” is a lower bound for a request that exceeded the client deadline. Measurements use live account state; snapshot slots and response sizes can differ between requests.