Content pfp
Content
@
0 reply
0 recast
0 reaction

Kevin pfp
Kevin
@typedarray.eth
Ponder is now 10-50x faster during historical indexing 0.4.37 introduces batched database writes & an in-memory cache for frequently accessed records Apps that use a remote database will be much faster
23 replies
31 recasts
297 reactions

Kevin pfp
Kevin
@typedarray.eth
Before, every store API method (create, findUnique, etc) hit the database Now, the store uses an in-memory record cache. When the cache gets too big, it flushes the N least recently used records to the database in a single query Release: github.com/ponder-sh/ponder/releases/tag/%40ponder%2Fcore%400.4.37
4 replies
9 recasts
99 reactions

Kevin pfp
Kevin
@typedarray.eth
Our perf goal is <1 minute for most apps, and <1 hour for massive apps (like Uniswap V2 across all chains) Another 2 orders of magnitude to go 🫡 We're hiring engineers in NYC across all roles - DM if interested! Chat: t.me/ponder_sh Docs: ponder.sh/docs/indexing/create-update-records
0 reply
0 recast
1 reaction