top | item 43609742 (no title) your_challenger | 11 months ago Has anyone tried analyzing Durable Object with SQL storage performance? Is it as bad as D1? discuss order hn newest ambigious7777|10 months ago I'm pretty sure D1 and DO build upon each other. I'm not sure exactly how, but I do remember reading about them using shared infra. manter|10 months ago D1 is built using Durable Objects - so in theory DO could be faster.AFAIK when you call D1 it's Worker > D1 (Durable Object) > local storage.So using DO directly would just be DO > local storage.I believe the connection between worker and D1 is the painful part, requiring multiple round trips. weird-eye-issue|10 months ago Its sub millisecond within the DO, completely different architecture cebert|11 months ago I am also curious to see these D1 vs DO comparisons if someone has. unknown|11 months ago [deleted]
ambigious7777|10 months ago I'm pretty sure D1 and DO build upon each other. I'm not sure exactly how, but I do remember reading about them using shared infra. manter|10 months ago D1 is built using Durable Objects - so in theory DO could be faster.AFAIK when you call D1 it's Worker > D1 (Durable Object) > local storage.So using DO directly would just be DO > local storage.I believe the connection between worker and D1 is the painful part, requiring multiple round trips.
manter|10 months ago D1 is built using Durable Objects - so in theory DO could be faster.AFAIK when you call D1 it's Worker > D1 (Durable Object) > local storage.So using DO directly would just be DO > local storage.I believe the connection between worker and D1 is the painful part, requiring multiple round trips.
ambigious7777|10 months ago
manter|10 months ago
AFAIK when you call D1 it's Worker > D1 (Durable Object) > local storage.
So using DO directly would just be DO > local storage.
I believe the connection between worker and D1 is the painful part, requiring multiple round trips.
weird-eye-issue|10 months ago
cebert|11 months ago
unknown|11 months ago
[deleted]