mirror of
https://github.com/koel/koel.git
synced 2026-04-26 17:25:59 +03:00
[GH-ISSUE #257] Very slow with giant libraries #188
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SamuelMoraesF on GitHub (Mar 3, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/257
My Koel instalation is very slow since I've added all my musics.
SELECT COUNT(*) FROM songs;returns 10943 results.Can you add an option(or something like) to search and manage all musics in server side?
@BernardGoldberger commented on GitHub (Mar 3, 2016):
I have nearly 10K songs without any issues.
@phanan commented on GitHub (Mar 4, 2016):
@SamuelMoraesF What version?
@SamuelMoraesF commented on GitHub (Mar 4, 2016):
I'm running the latest version (v2.1.0).
On my smartphone, Koel is slow in every action(play/pause a music, change to artists/albums page...) at Firefox for Android, I've tried on Moto X and Moto G devices. With Google Chrome it works normally.
On my computer, Koel is running normally, but when I search for something, it take ~5 seconds to reply(and seems to use a lot of memory, as my browser animations stop) this happens with my smartphone too(with any browser).
@phanan commented on GitHub (Mar 5, 2016):
@SamuelMoraesF Thanks. That seems to be #231, which has been fixed on the
masterbranch. I'm still finishing several remaining issues before bumping up the tag, but you can try usingmasterfor now (it's pretty stable).