If you only do storage ops DOs use a very minimal duration 🙂 As an example I have a DO that only d

If you only do storage ops DOs use a very minimal duration

As an example I have a DO that only does storage ops... Total of 34,486,510 requests and only 83,293 GB-sec for last month

UnsmartOP•3/9/23, 5:12 PM

If I did my math correct thats $1 of duration charges for 34.5 million requests

UUnsmart If you only do storage ops DOs use a very minimal duration 🙂 As an example I h...

johtso•3/9/23, 5:17 PM

By short lived I mean the data is short lived

johtso•3/9/23, 5:17 PM

Like a DO representing a payment process

UnsmartOP•3/9/23, 5:17 PM

I see

johtso•3/9/23, 5:18 PM

So more like a function that might take a little while to complete, but needs to be durable in the case of temporary failure

UUnsmart If I did my math correct thats $1 of duration charges for 34.5 million requests

Kevin•3/9/23, 6:49 PM

Let’s hope you did the math correctly then!

Kevin•3/9/23, 6:53 PM

A small amount of DOs being frequently accessed seems pretty safe… the danger I’ve found is when you’re creating a LOT of DOs.

For instance, on itty.sh, I originally spun up a DO a for every entry created, just for a setAlarm to destroy it at expiration. That worked like a dream, but was gonna eat my lunch in the bill for every 128MB DO spun up. Instead, I had to create a a series of expiration managers, basically load balanced expiration DOs, each handling potentially many expirations.

Kevin•3/9/23, 6:53 PM

so much more complex, sadly

UnsmartOP•3/9/23, 7:21 PM

I do 2 requests per minute per DO I have which is what the 34.5 million requests are

dctanner•3/10/23, 2:14 PM

Where is best to submit a suggestion for the docs?

dctanner•3/10/23, 2:15 PM

I couldn't find any mention of receiving SSE responses within a worker or DO, using the fetch api instead of EventSource. Eventually I found https://github.com/julienmachon/sse-client which works pretty well. It'd be nice if the docs just mentioned receiving SSE is possible in a DO.

GitHub

GitHub - julienmachon/sse-client: Server-sent event client using th...

Server-sent event client using the fetch API. Contribute to julienmachon/sse-client development by creating an account on GitHub.

dctanner•3/10/23, 2:15 PM

I'm sure you can guess what this is for.... receiving streaming ChatGPT api responses

UnsmartOP•3/10/23, 9:38 PM

That code base is really hard to follow, can you be more specific on where the problem is?

johtso•3/11/23, 11:28 AM

How do Workers Trace Events logs work when it comes to durable objects?

johtso•3/11/23, 12:42 PM

Does the durable objects list endpoint return in lexicographic order the same as the KV list endpoint?

johtso•3/11/23, 12:42 PM

Not mentioned in the API docs

Jjohtso Does the durable objects list endpoint return in lexicographic order the same as...

DaniFoldi•3/11/23, 1:02 PM

I believe it does, at least according to behaviour I've seen, and quoting from the docs

reverse: booleanreverse: boolean
If true, return results in descending order instead of the default ascending order.
Note that enabling this does not change the meaning of start, startKey, or endKey. start still defines the smallest key in lexicographic order that can be returned (inclusive), effectively serving as the endpoint for a reverse-order list. end still defines the largest key in lexicographic order that the list should consider (exclusive), effectively serving as the starting point for a reverse-order list.

DDaniFoldi I believe it does, at least according to behaviour I've seen, and quoting from t...

johtso•3/11/23, 1:07 PM

Ahhh.. but the IDs are derived from the names so I guess not useful

johtso•3/11/23, 1:07 PM

Unless the IDs have the creation time at the beginning?

DaniFoldi•3/11/23, 1:08 PM

Ah are you referring to https://developers.cloudflare.com/api/operations/durable-objects-namespace-list-objects ?

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

johtso•3/11/23, 1:08 PM

Yep

johtso•3/11/23, 1:08 PM

Where did your quote come from?

DaniFoldi•3/11/23, 1:08 PM

I don't think there are any guarantees around the ordering there

Jjohtso Where did your quote come from?

DaniFoldi•3/11/23, 1:09 PM

That's for the storage list operation

johtso•3/11/23, 1:09 PM

Was just hoping to be able to query recent objects without having to store Extra references somewhere

johtso•3/11/23, 1:21 PM

Is there any reason I couldn't run a website in a durable object?

johtso•3/11/23, 1:22 PM

Would there be big performance issues?

Jjohtso Is there any reason I couldn't run a website in a durable object?

Hello, I’m Allie!•3/11/23, 1:27 PM

The biggest limitation is the limit of ~100 RPS

johtso•3/11/23, 1:28 PM

Oh nice, that's plenty enough for me

johtso•3/11/23, 1:28 PM

I guess you also need to make sure not to block the gates?

johtso•3/11/23, 1:30 PM

For me one location is better, all requests are going to be from the same place

johtso•3/11/23, 1:30 PM

And it means I can use kv without cache staleness issues

johtso•3/11/23, 1:33 PM

Do you know of a nice DO based rate limiting example? I feel like there might have been a blog post..

johtso•3/11/23, 1:58 PM

I guess it's not really a DO thing as it doesn't even need persistence

johtso•3/11/23, 1:58 PM

just need a good in-memory rate limiter implementation

johtso•3/11/23, 2:10 PM

I guess that's true as long as my rate limiting only cares about a window of 10 seconds or less

Jjohtso I guess that's true as long as my rate limiting only cares about a window of 10 ...

DaniFoldi•3/11/23, 2:12 PM

*30, DOs stick around for 30 seconds after a request

johtso•3/11/23, 2:13 PM

good to know, I think the docs say a minimum of 10s

johtso•3/11/23, 2:13 PM

"In the absence of failures, in-memory state should not be reset after less than 10 seconds of inactivity."

johtso•3/11/23, 2:14 PM

but I guess that's the pessimistic number

johtso•3/11/23, 2:15 PM

I wonder if it's better to implement a rate limiter as a proxy or just as an api that returns whether a request should be allowed..

johtso•3/11/23, 2:15 PM

I guess a proxy would be more efficient

johtso•3/11/23, 2:16 PM

but probably only very marginally?

johtso•3/11/23, 2:25 PM

@skye_31 hold on a minute, if I hosted my website in a DO wouldn't everyone's requests block every time I made a fetch to another DO / worker?

johtso•3/11/23, 2:25 PM

or is that input output gate stuff only for storage operations?

If you only do storage ops DOs use a very minimal duration 🙂 As an example I have a DO that only d

Similar Threads