-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aggressive caching of images can make site slow #776
Comments
Could you share an url where this is happening? I tried with https://lemmy.ml/c/memes which has many image posts, but Firefox dev tools only show 46 requests and 3.76 MB / 1.98 MB transferred (cache disabled). |
Is this from a community or home, or from the post page? |
It's from home. But i don't think it's a an issue anymore. We can close it for now. |
I think this is still an issue and not only because of the images, but also because all posts are completely fetched from the home or any community list view. Would there be an option to only fetch the first x characters of the posts for the list view? Also on my mobile I experience a slow, almost freezing view when switching to and back to the list of posts. |
You need to provide specific steps to reproduce this, including a specific url where this happens. Also mention which browser, os etc you are using. |
The home.tsx shouldn't be loading any images other that the one linked in the url. The post bodies might contain images but those aren't rendered as markdown. |
@dessalines Well that is not what lemmy does. Tippy.esm.js seems to trigger the download: Can tippy be configured or disabled maybe by config? I guess that here md.render is fetching all content?
|
I can confirm that removing the tippy feature from the post (commenting those lines in post-listing.tsx) list does workaround this problem. |
Hrm... didn't think about that. Might need to make sure tippy doesn't do html rendering. |
Issue Summary
With many images in posts that show up on the initial page after login, lemmy is caching all those images (from browser requests). Even if the user does not open these posts. If you have hundreds of images, this really slows down the initial page load.
Is there a way to reduce this caching and thus reduce requests and traffic to nginx/lemmy-backend?
Steps to Reproduce
Technical details
Lemmy 0.16.6
The text was updated successfully, but these errors were encountered: