@Erisa | Support Engineer if that helps here is what the worker logic looks like that serves that cs

@Erisa | Support Engineer if that helps here is what the worker logic looks like that serves that css file, see the /build/ branch

https://gist.github.com/kof/914c593049325eda72b25ad392737647

Gist

dynamic dispatcher

dynamic dispatcher. GitHub Gist: instantly share code, notes, and snippets.

Erisa•2/18/24, 7:05 PM

env.STATIC_ASSET_CDN_ORIGIN

env.STATIC_ASSET_CDN_ORIGIN

an R2 public bucket with Custom Domain?

OOleg Isonen @Erisa | Support Engineer if that helps here is what the worker logic looks like...

bun•2/18/24, 7:08 PM

i dont see u using caching here. i believe you can just add

cf

cf

properties to the

fetch

fetch

request

EErisa Is `env.STATIC_ASSET_CDN_ORIGIN` an R2 public bucket with Custom Domain?

Oleg IsonenOP•2/18/24, 7:08 PM

correct

Ivan Starkov•2/18/24, 7:09 PM

It's cached by default fetch behavior it's seen with

Cf-Cache-Status: HIT

Cf-Cache-Status: HIT

header

Original message was deleted

bun•2/18/24, 7:11 PM

yeah but does it retrieve the response from disk cache or still make a request?

bun•2/18/24, 7:15 PM

wdym both? it should display (disk cache) if it actually retrieves the asset from chrome cache

bun•2/18/24, 7:15 PM

why doesnt it do the same for

favicon

favicon

? maybe its because content-type is not provided for this css asset? its still odd. i dont see this behaviour for traditional websites network request flows

Original message was deleted

Oleg IsonenOP•2/18/24, 7:17 PM

that's interesting and I am just

how it can be an unsolved problem out of the box in a straight forward way, because its not like I am trying to shave off 20ms, I am talking real shit-show slow, 500ms in many edges means we are not passing core web vitals "because we are serving static assets too slow" and that's a crazy problem to have in 2024

SSoulHarsh007 👋 I am using rclone to upload files to my s3 bucket, and today I found this ver...

dave•2/18/24, 7:17 PM

If possible, I really recommend everyone avoid multipart uploads.

OOleg Isonen that's interesting and I am just 🤯 how it can be an unsolved problem out of the...

bun•2/18/24, 7:21 PM

i get 10 ms for that css

Ddave If possible, I really recommend everyone avoid multipart uploads.

SoulHarsh007•2/18/24, 7:21 PM

Yep, I reuploaded the file without multipart, because one of our tooling depends on the etag being md5sum ^^

Bbun i get 10 ms for that css

Oleg IsonenOP•2/18/24, 7:21 PM

that's nice, must be a cache hit, though even with cache hit its usually 50ms, you must be living in the datacenter or you are testing it wrong

Oleg IsonenOP•2/18/24, 7:22 PM

150 is more like it when its not too far away from european R2

Oleg IsonenOP•2/18/24, 7:23 PM

150ms with cache hit is a s..t show as well in my opinion

Erisa•2/18/24, 7:24 PM

That will also heavily depend on the internet connection and routing quality of the individual requesting it. For example I would probably get 150ms if I used my phones mobile data or had an ISP with poor quality peering

Erisa•2/18/24, 7:25 PM

There are two ends of every connection

EErisa That will also heavily depend on the internet connection and routing quality of ...

Oleg IsonenOP•2/18/24, 7:27 PM

you can compare with this static file to see clear difference https://eu.posthog.com/static/array.js

Unsmart•2/18/24, 7:28 PM

thats exactly the same speed for me on cache miss and cache hit from texas

(compared to yours)

Oleg IsonenOP•2/18/24, 7:29 PM

actually this one seems doing well https://cdn.jsdelivr.net/npm/psl/dist/psl.min.js

Unsmart•2/18/24, 7:29 PM

cloudflare seems to do much better when cached though the posthog aws one seems to have higher end latencies when refreshing multiple times

Original message was deleted

Oleg IsonenOP•2/18/24, 7:29 PM

that would be an acceptable performance to me if its globally in that range, I am talking really 500ms bad globally, not trying to shave off 20ms

bun•2/18/24, 7:31 PM

bun•2/18/24, 7:31 PM

its like 200 ms

bun•2/18/24, 7:31 PM

globally

Bbun Click to see attachment

Oleg IsonenOP•2/18/24, 7:31 PM

what resource are you going for with this test, the document? we are discussing static asset, e.g. this one https://webstudio.is/build/_assets/index-6JJ5GLFW.css

bun•2/18/24, 7:31 PM

yeah

Oleg IsonenOP•2/18/24, 7:31 PM

document is not an issue here, even though it could be faster

bun•2/18/24, 7:32 PM

the path param is hidden in settings but its for that url

Oleg IsonenOP•2/18/24, 7:32 PM

@bun what's the tool you are using?

bun•2/18/24, 7:32 PM

https://www.jsdelivr.com/globalping

bun•2/18/24, 7:32 PM

Bbun https://www.jsdelivr.com/globalping

Oleg IsonenOP•2/18/24, 7:33 PM

global ping doesn't even try to fetch a specific resource

bun•2/18/24, 7:33 PM

its not a ping its a http request

Original message was deleted

Oleg IsonenOP•2/18/24, 7:33 PM

CAN'T because it doesn't work with R2 apparently

bun•2/18/24, 7:34 PM

TTFB is what matters here

Bbun its not a ping its a http request

Oleg IsonenOP•2/18/24, 7:34 PM

to the document, and we are not discussing that, we need that test to the css ressource I mentioned and that tool doesn't let me specify the ressource

Original message was deleted

Oleg IsonenOP•2/18/24, 7:35 PM

what's a normal host? our static ressources are on R2

OOleg Isonen to the document, and we are not discussing that, we need that test to the css re...