A place for developers to talk about building on Farcaster.

/dev

surprising 10x speed up in throughput with this change:

Before:
- await promise 1
- await p2
- await p3
- await p4

After:
- await [p1, p2]
- await [p3, p4]

Running node.js. Expected minor speed up. Underestimated cost of context switching.

Startups / software / traveling / skydiving / running

building • prev manifold.xyz, twilio.com

👨‍💻 /uno and /outside, @unofficial

yep, didn’t bother cause I thought speed up would be irrelevant. wrong.

Was that simple; diff below.

context: this is a standard http request handler, does about 1rps. The subroutines here are not expensive. I was expecting a minor speed up in proportion to request duration but median request went from ~1500ms to ~70ms.

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

Was that simple; diff below.

context: this is a standard http request handler, does about 1rps. The subroutines here are not expensive. I was expecting a minor speed up in proportion to request duration but median request went from ~1500ms to ~70ms.

https://gist.github.com/jtgi/a9d9694186360df255481466fd19fac8

Building @warpcast and @farcaster, new dad, like making food

saving await [p1 … p4] for a rainy day?

👀 

[notifs on for before/after graph]

was my attempt to be language agnostic lol

Holup what JavaScript wizardry is this notation?

Go on Promise.all, Promise.allSettled
Bluebird is good too for handling promises
And in remix-utils for remix, you have the awesome “promiseHash”

If you have one that is dependent of a previous, but not all dependent on previous, a combo of Promise.all and .then on the needed one could be a good idea

I try using promise.all() by default wherever  I can.