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

ftintitle: extremely slow #2281

Closed
mfiano opened this issue Nov 24, 2016 · 4 comments
Closed

ftintitle: extremely slow #2281

mfiano opened this issue Nov 24, 2016 · 4 comments
Labels
needinfo We need more details or follow-up from the filer before this can be tagged "bug" or "feature." stale

Comments

@mfiano
Copy link

mfiano commented Nov 24, 2016

ftintitle plugin, when called manually after import takes an incredibly long time to complete - infact the import with all the MB queries was faster. On top of this, its output printed seems to be in a completely random order, with several minutes between each line printed. Also the CPU usage is between 1-30% for a single CPU core for beets. It's as if it is mostly idle.

@sampsyo sampsyo added the needinfo We need more details or follow-up from the filer before this can be tagged "bug" or "feature." label Nov 25, 2016
@sampsyo
Copy link
Member

sampsyo commented Nov 25, 2016

That's odd. A quick test here didn't reproduce the problem:

$ time beet ftintitle
beet ftintitle  0.50s user 0.16s system 97% cpu 0.670 total

Can you please include your configuration and a verbose log? And perhaps check whether this happens for some tracks but not for others?

@mfiano
Copy link
Author

mfiano commented Nov 25, 2016

I ran watch lsof ... to check out exactly what it was working on, and it seems to spend a long time on flac files compared to lossy files. I suspect it is reading the whole file stream and then writing the whole thing back to disk when it writes the tags, probably with a really small chunk size.

@sampsyo
Copy link
Member

sampsyo commented Nov 25, 2016

OK! But your configuration and the verbose log would still be helpful.

@stale
Copy link

stale bot commented Jul 12, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 12, 2020
@stale stale bot closed this as completed Jul 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needinfo We need more details or follow-up from the filer before this can be tagged "bug" or "feature." stale
Projects
None yet
Development

No branches or pull requests

2 participants