Skip to content
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

[BUG] DB & page slowdown at high snippet counts #71

Open
jordan-dalby opened this issue Nov 14, 2024 · 1 comment
Open

[BUG] DB & page slowdown at high snippet counts #71

jordan-dalby opened this issue Nov 14, 2024 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@jordan-dalby
Copy link
Owner

Describe the bug
At high snippet counts (>500), the page will start to slow (on my machine) since all snippets are rendered at once. It's especially bad when importing a large number of snippets at once, the DB might be struggling to keep up.

To Reproduce
Import 500 snippets at once, wait for page reload

Expected behavior
No performance difference

Screenshots
n/a

Platform
All

Additional context
May be worth migrating to postgresql eventually, would be a good intermediary for user accounts anyway, since sqlite won't support concurrent users.
Snippets should probably be (invisibly) paginated, although we'd need to figure out how to make that work with the current API.

@jordan-dalby jordan-dalby added the bug Something isn't working label Nov 14, 2024
@vlavrynovych
Copy link

To fix this type of problem you'll need to re-work your search bar. Once it start to do a lookup to the database you will be able to implement an infinity scroll.

IMHO infinity scroll was never the best option, I always prefer pagination.

With a migration to postgresql and work on user accounts you'll probably need to replace docker parameters of username, password and the tocket by classic registraction like on the Open WebUI or Portainer.


As for me, this problem will be a real proble only for a real geek who live with his snippets. I mean that the level of effor needed to solve it today prbably does not worth your time at this stage. I personally would move it for a backlog for a few month to hear about it from a real users. Once you have a big fan base it all will make a ton of sense.

@jordan-dalby jordan-dalby added this to the Backlog milestone Nov 17, 2024
@github-project-automation github-project-automation bot moved this to Backlog in ByteStash Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants