https://discord.cloudflare.com logo
Join Discord
Powered by
# r2
  • a
    Is there any difference between how Workers bindings and the S3-compatible API is handled that could affect performance?
  • v
    I think Workers bindings have less auth overhead in front of it. I don't know if that'll actually matter though because it wouldn't be an IOPS bottleneck, just a latency one
  • i
    Those are basically DDoS machines under a different name 😛
  • a
    Gotcha. Can I assume a read/write is successful if the `.get()`/`.put()` promise resolves?
  • v
    Yup
  • j
    curious: any reason why the 
    R2Object.version
    seen from the binding is not returned as the 
    x-amz-version-id
    header in 
    Get/HeadObject
    ?
  • a
    Well, the Workers logstream clearly can't handle this. I'll need to find a better way to count 😂
  • i
    Barely anything can handle that 🤪 I’m gonna watch the status page, you are gonna break Cloudflare 🤣🤣
  • k
    won't be the first incident he's caused
  • k
  • a
    I would usually set up an atomic counter with DOs for something like this, but I don't think that'll work...
  • i
    The latency, yeah…
  • i
    And DOs are write limited.
  • a
    Copy code
    mjs
export class Counter {
    constructor() {
        this.value = 0
    }

    async fetch() {
        return new Response(this.value++)
    }
}
  • a
    this should work
  • a
    it'll be kept alive by the constant requests
  • i
    Yeah, but you're not gonna hit over about 100 req/s with that, right?
  • a
    No idea - I'll try
  • s
    workers uses javascript right?
  • i
    Yup.
  • i
    Was thinking about the same limit, but maybe they are only to storage writes.
  • i
    Was pretty sure it was throughput but who knows?
  • s
    i feel like im learning fake JS in school now
  • i
    "Durable Objects scale well across Objects, but each object is inherently single-threaded. A baseline of 100 req/sec is a good floor estimate of the request rate an individual Object can handle, though this will vary with workload."
  • i
    Sounds like any requests, not just storage writes.
  • a
    a few hundred requests a second so far - not seeing any slowdowns yet
  • i
    Then yeah, not gonna work very much.
  • e
    the GQL analytics api expose health checks metrics, so you can pull the stats you need 👀
  • a
  • a
    (count is total number of reads)
1...666768...1050Latest