Joe Petrich 🟪 on Warpcast

Content pfp

0 reply

0 recast

0 reaction

Joe Petrich 🟪 pfp

Joe Petrich 🟪

An engineer on my team has been working on a migration of some indexed blockchain data to postgres and took our queries from an initial average latency of almost 2 seconds to under 100ms. The process to get there was fascinating, imo. Would anyone else be interested in a writeup of the optimization techniques he used?

11 replies

2 recasts

28 reactions

welp 🎩🌸 pfp

Yeah, of course. What was this migrated from?

1 reply

0 recast

0 reaction

Samuel ツ pfp

@samuellhuber.eth

0 reply

0 recast

0 reaction

Pierre H. — q/dau pfp

Pierre H. — q/dau

I'd be interested 🙌 sharing in return our experience at Ledger serving web3 data at web2 scale :)) https://www.ledger.com/blog/serving-web3-at-web2-scale

2 replies

0 recast

1 reaction

Royal pfp

I am super curious about it and how it compares to the tech that @notnotstorm is using with Cryo

1 reply

0 recast

2 reactions

Eddy Lazzarin 🟠 pfp

Eddy Lazzarin 🟠

For the Ethereum to Postgres usecase, I've heard that people really like @indexsupply's Shovel project, which is extremely fast: https://indexsupply.com/shovel/

0 reply

0 recast

2 reactions

kerman pfp

0 reply

0 recast

0 reaction

datadanne pfp

0 reply

0 recast

0 reaction

Shashank pfp

subgraphs from the graph protocol were supposed to be the solution here and somehow they ended up over optimizing for tokenomics and less of developer experience @ponder might be an interesting solution for this use case as well

0 reply

0 recast

0 reaction

🦒 pfp

0 reply

0 recast

0 reaction

Ivy pfp

0 reply

0 recast

0 reaction

Ivy pfp

0 reply

0 recast

0 reaction