-
Notifications
You must be signed in to change notification settings - Fork 6
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
Trouble analyzing library #47
Comments
Hi, This should indeed not happen. I think part of it is due to the way Thanks for reporting, I'm on it. |
Hi again! It seems that someone has the same problem as you, and I'm trying to address the root cause (which doesn't seem to be MPD / rust-MPD themselves). |
@brawnswubb now that I think about it - could you try to run |
Update, it seems like you can "fix" it by running the analyzer with a lower number of cores (see #56 (comment)). Maybe try with 2 or 4 cores, and see if it works? |
Hello,
Running blissify 0.3.8 on Arch Linux with a MPD library of over 300k songs
When I set
log_level = "verbose"
in mpd config I see that the output buffer is full when running blissify initIn order for blissify to run successfully
max_output_buffer_size
has been set to a high valuePrior to setting the arbitrarily high value, a Output buffer is full was observed at the 16384 and 32768 values.
I set
max_output_buffer_size
to "323684" in order for it to run. Earlyoom kills programs once my current RAM is less than 1% available.Blissify is terminated after some time analyzing.
Is there a way to adjust what Blissify is requesting from the MPD server?
The text was updated successfully, but these errors were encountered: