caching?
Answered
Ruwbix posted this in #help-forum
RuwbixOP
Hi I have a server on steam. I have a website that is integratied with the in-game chat (using postgres database).
Now I have a little issue... I want to display profile pictures for each user. My current implementation is getting all the steam profile through api from all the unique steamids from the messages everytime a new message is send.
Well say I have 100 messages and 40 unique users- it'll pull 40 steam profiles (at least) on each new message.
Not sure how I would go about this... any tips?
Now I have a little issue... I want to display profile pictures for each user. My current implementation is getting all the steam profile through api from all the unique steamids from the messages everytime a new message is send.
Well say I have 100 messages and 40 unique users- it'll pull 40 steam profiles (at least) on each new message.
Not sure how I would go about this... any tips?
Answered by aardani
you can cache your fetches.
for example:
for example:
revalidate: 60 will cache fetch result up until 60 second57 Replies
you can cache in next.js for a certain amount of period
you can either:
1. cache a full route
or
2. cache only the data but keep rendering dynamic
1. cache a full route
or
2. cache only the data but keep rendering dynamic
RuwbixOP
We're running 3 servers and we should be storing like 2/3 strings (for now) for each user. Will be stored for a max of 24h as chats reset at midnight
how is the data accessed?
from where to where?
RuwbixOP
Well so we get the steamid (which never changes) from the messages table. But we have to fetch the name + profile pic url through the api as those can change at any given time
what does your current implementaiton looks like?
@Ruwbix Well so we get the steamid (which never changes) from the messages table. But we have to fetch the name + profile pic url through the api as those can change at any given time
if you want to cache it then you need to give up the idea that "name + profile pic has to be fresh coz they can change at any given time"
caching means that its okay to be outdated/stale for an amount of time
RuwbixOP
I can live with it being outdated for a bit
you can cache your fetches.
for example:
for example:
revalidate: 60 will cache fetch result up until 60 secondAnswer
the
fetch() api is already modified to allow this kind of caching.unless you are using external fetching libraries, there is another way
RuwbixOP
So that would refetch all existing ids each 60s but still fetch like unique ids?
It can be much longer than 60s tbh
at 61st second, it will still show up old data but the first request that is stale will do a background revalidation that will pull up new data on the subsequent request
tbh the duration can be up to you
RuwbixOP
But this would handle like a message every few seconds for like a lot of messages and users
yeah good then
i dont see a problem with that
RuwbixOP
Is that done server sided or client sided?
server sided
the cache is unique for every URL
so if i fetch for user1, it wont replace cache of user2
RuwbixOP
And what if that URL is dynamic? Or like has these ?example=true
for every URL
cache for
user1 and cache for user1?example=true will be differentRuwbixOP
Well thats an issue in that case :/
why would it be?
RuwbixOP
Because it also has a leaderboard implemented on that same page in which the chat is. So like when you say filter based on most kills the url would change
i thought you only want to cache the name and the images
you need to separate the data in different URLs to control which data you want to cache
@aardani i thought you only want to cache the name and the images
RuwbixOP
I do. But like the chat is like a little box on the site which you can open/close. It's like a little modal on the leaderboard page
@Ruwbix Because it also has a leaderboard implemented on that same page in which the chat is. So like when you say filter based on most kills the url would change
the next.js url would change but would the url fetch to the data source change?
RuwbixOP
I'm using a socket to fetch unique messages every few seconds
Just checking on that page if a new "message" event is triggered and that'll fetch like names + profile pics
yes
you cache the
names + profile pics part not the socket url partits a cache thats used in the server that has nothing to do with the client. Client only see the data
its a cache that doesn't have anything to do with how Client access the Next.js URL
RuwbixOP
So it doesnt matter if the URL parameters change?
Because they definitely will
Im not fetching through the socket
Or how do I say it... whenever I get a new socket event I start fetching name + profile
If you are doing data fetching in the server through the same URL regardless of where it come from then it doesn't matter
in route
in route
in route
the cache will be the same
in route
/a you could fetch('https://.../getUserID') in route
/b you could fetch('https://.../getUserID') in route
/c you could fetch('https://.../getUserID') the cache will be the same
RuwbixOP
Ah okay
@Ruwbix Ah okay
so the URL where client access from doesn't matter
it has nothing to do with the cache
the Data cache only caches based on the
it has nothing to do with the cache
the Data cache only caches based on the
URL of the fetch(url) function in the serverits a data cache, not a route cache
2 different thing
RuwbixOP
so if I fetch(player1), and then 30s later I fetch(player1) again it wouldn't matter as it's cached?
yeah
it doesn't care where the
fetch takes placeRuwbixOP
Ahhh okay yeah that makes much more sense
Sorry im not natively english, but what you were saying made sense haha
No problem