"Use Cache" on Vercel
Unanswered
Yellow-breasted Bunting posted this in #help-forum
Yellow-breasted BuntingOP
I have had troubles with "use cache" on Vercel for the past hours. I never realized that this was going to be an problem and I thought my app was finished until it was deployed. I am really stressed out so I can't really grab my mind together so I am kind of required of assistence. I tried making use of Chat-GPT, but that didn't work out either.
I am on Next.js 16.1.0 and I use Supabase, my main concern is a table of 19000 rows being fetched that isn't cached properly anymore.
I am on Next.js 16.1.0 and I use Supabase, my main concern is a table of 19000 rows being fetched that isn't cached properly anymore.
9 Replies
Yellow-breasted BuntingOP
I didn't know the data cache could be full? Also it's probably not because "use cache" in general doesn't work on Vercel due to it being serverless and the memory is epehemeral
@Yellow-breasted Bunting I didn't know the data cache could be full? Also it's probably not because "use cache" in general doesn't work on Vercel due to it being serverless and the memory is epehemeral
Data cache on Vercel cn be full. You can see it in the vercel usage dashboard
Data cache isnt a memory cache. Its a regional file cache that vercel provides so you can access data faster
See more here: https://vercel.com/docs/data-cache
Not to mention, nextjs uses several different caching strategies when "use cache" is presented which vercel definitely support on their platform
American Crocodile
What is the problem? Is it the revalidation or the fetching of the cached data? Is the data being fetched every time even though it should be cached?
If the data cache is full, can we use pagination to fetch it in smaller chunks?
Do we need all 19,000 rows displayed at once or can we click through them one page at a time?