A refresh is a new request, your server doesn't see a difference.
If you have parts that are called a lot but didn't change much it is possible to cache them.
Personally I should first check if there are improvements in the code before caching because that can result in other problems.
But for some parts a cache is a valid option.
Example:
For this site are the top members and moderators cached for 30 minutes. That is data that isn't changed much and isn't a problem if it isn't updated in realtime. But it is displayed on a lot of requests.
See: https://github.com/laravelio/laravel.io/blob/main/app/Http/Controllers/Forum/ThreadsController.php#L59-L64=
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community