100k requests - what does it mean?
Hey guys,
can you please tell me what this means?
100k requests for what exactly, visitors?
I only have one static website...
What happens if the 100k is reached, I dont even know how I got the 9k till now
26 Replies
I curl your Worker:
curl https://worker_name.konstandin.workers.dev, that's one request.
This is also affected by bots visiting your WorkerOkay wait what is a worker XD
Cloudflare Docs
Cloudflare Workers · Cloudflare Workers docs
Cloudflare Workers provides a serverless execution environment that allows you to create new applications or augment existing ones without configuring or maintaining infrastructure.
Okay, if I understand it correctly it takes up some loading on the server instead of the client? Sorry man, I am a beginner
Yeah, basically it just runs some code in Cloudflare's datacenters
It's a bit more complex than this, but that's a small gist
But the site will work normally if it hits 100k yes?
Just the client has more work to do no?
It depends on how the app is built. Some will handle it gracefully, but others may break entirely
As I said, I just have a simple portfolio, no fancy stuff, some framer motion, but that all is "use client"
Does building a page on CF take up these credits too?
Assuming that it is fully static, you shouldn't be consuming any requests. Do you have a repo for your project?
I'm sorry, I can't share it. My guess is that probably building the websites after I commit take up the requests, is this possible?
Or DNS stuff?
Google Fonts import urls, image urls or NextJS image optimization wouldn't use up workers/functions, correct?
Oh, if it is NextJS then yes, it burns through requests pretty fast, unless you do a full static build
Building doesn't consume any requests
It's just request made by the browser
So what can I do then?
I cant switch NextJS xd
If you can use a static build, I would probably do that
okay, need to learn what that is
Otherwise, you can use Workers Paid, which removes the limit
Yeah I saw that
I will try to have a static build first though
I did select the Framework preset as NextJS instead NextJS (Static HTML Export), can this be the issue? If yes, if I redeploy the site with the correct preset, do I have to make changes to the code too?
Changing the preset shouldn't make a difference, your project needs to be configured to build as a static project first
>.<
If you use API Routes in your project, you can't go static, for example
I dont have any APIs whatsoever
Can I DM you a link ?
Ok nevermind, I think I got it static now. I will see if the rates increase further
It seems like they have not increased further (+1 request instead of hundreds)
Will watch it tomorrow again, Thank you so much for your help!!!
@Hard@Work No workers used anymore. Nice! However I still wonder, what the exact difference now was. What used the workers, while the site was non-static? I would like to implement a automatic language detection based on the accept-header, but I think I would need to have a non-static site for that? Then I would have the same problem again xD
if you were using Cloudflare Pages, NextJS probably auto-generated a function, which is billed the same as workers.
Okay, how can we disable these specific functions? I don't quite get it...
it sounds like you already did, if you specify nextjs to build a static-only site
Thats correct, however I would like to have the locale auto-detected, this is probably not possible with static pages?
or am I wrong?
you could probably do it client-side, but the main issue with that is that people would see the default language first before js loads (assuming youre doing static ssr)
Yeah, thats annoying
thats why I wondered where these random requests come from, to stop them and use them for something useful like the locales
localization
Yeah, middleware doesnt work with static pages