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

Trouble analyzing library #47

Open
brawnswubb opened this issue Jan 8, 2024 · 4 comments
Open

Trouble analyzing library #47

brawnswubb opened this issue Jan 8, 2024 · 4 comments

Comments

@brawnswubb
Copy link

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 init

Jan 07 23:08 : client: [4] opened from 127.0.0.1:43290
Jan 07 23:08 : client: [4] process command "list "file""
Jan 07 23:08 : client: error on client 4: Output buffer is full
Jan 07 23:08 : client: [4] command returned 0

In order for blissify to run successfully max_output_buffer_size has been set to a high value
Prior 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?

@Polochon-street
Copy link
Owner

Hi,

This should indeed not happen. I think part of it is due to the way rust-mpd handles the list / search for all your songs; I've opened a bug report, and most likely will have to change some things in blissify myself.

Thanks for reporting, I'm on it.

@Polochon-street
Copy link
Owner

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).
This branch #58 should fix the buffer size problem, but now I am trying to diagnose the OOM, which I can't seem to reproduce. Is your setup special in any way that could give us a hint on how to solve it?

@Polochon-street
Copy link
Owner

@brawnswubb now that I think about it - could you try to run RUST_LOG=debug blissify init --number-cores 1 path/to/library and tell me if it always fail on the same song? I'm thinking maybe a specific song is causing the problem :)

@Polochon-street
Copy link
Owner

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? blissify init --number-cores 2 /path/to/library

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants