https://discord.cloudflare.com logo
Join Discord
Powered by
# durable-objects
  • v
    i am aware of doing inside the worker
    Copy code
    let { readable, writable } = new TransformStream()
        request.body.pipeTo(writable)
  • k
    Same code should work in durable objects.
  • v
    but how would i forward the POST request into the DO? same as a websocket? and negotation the transformstream inside the DO?
  • v
    also this pipe way, is for streaming 2 requests into eachother (example using workers as a proxy) but i did not see a way to read the chunks on the fly
  • k
    Your stateless worker can directly forward a request it received to a DO, like 
    objectStub.fetch(request)
    where 
    request
    is the original request it received...
  • v
    so get into the DO like this from the worker?
    Copy code
    let id = env.OBJECT.idFromName('user1')
        let obj = env.OBJECT.get(id)
        return obj.fetch(request.url, request)
  • k
    just 
    obj.fetch(request)
  • v
    yes in my case the request is streaming (so it has many chunks sent over a period of 30+seconds)
  • k
    that's fine, streaming will work
  • k
  • v
    any idea then on the DO end how to get a callback for data chunk on the body? guessing some kind of pipe needs to be extracted from request.body() ?
  • k
  • v
    yes but I want the other end of the stream to dump into the DO memory
  • v
    that example only shows how to connect a pipe, (example to proxy a request betwwen another endpoint) so when the endpoint writes, it wont stall waiting for full reply)
  • v
  • v
  • v
    ah yea but no biggie
  • v
    kk working..
  • v
    oh wait this probably wont work because the DO will die once it exceeds the CPU limit (single fetch request CPU limit)?
  • k
    Yes, the CPU limit only get refreshed each time a new request arrives. Stream chunks don't count and new requests. Currently the limit is 500ms, but will be extended to 30s when we start billing -- maybe that's enough?
  • v
    500ms not enough, 30s probably
  • v
    Copy code
    while (1) {
        var view = new Uint8Array(8388608);
        const { value, done } = await reader.read(view);
        if (done) {
            break;
        }
    }
  • v
    i read for some reason the 
    view
    becomes detatched here, no idea what detached means. does it mean it cannot be reused? this code seems really silly
  • v
    the buffer should obv be reused? (declared outside the loop)
  • v
  • w
    I did a similar math on my side and im keeping the memory cache for the same reason. I read 100-1000x more from memory than from storage accounting everytime the object is (for any reason) reinitialized. If read from cache can have a lower price tier i will probably remove my memory map.... apps are constrained by cost all the time, thats not a surprise.
  • w
    Thats explain few erros that i got... Nice to know!
  • v
    yea basing costs of AWS is silly too as its just so overpriced inherently and many of their payment models dont make sense in relation to the underlying costs of the hardware/network
  • v
    example pricing things in "requests" why not just measure the instructions executed using eBPF or something and give a price per instruction based on clockcycles taken
  • v
    @User any idea why this is so expensive
1...131132133...567Latest