easytag is very very slow

Bug #129482 reported by Robert Persson
62
This bug affects 12 people
Affects Status Importance Assigned to Milestone
easytag
Expired
Medium
easytag (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: easytag

Easytag is very slow compared to, say, Ex Falso at batch editing tags. It takes several times as long to do the task.

It is also extremely slow at batch renaming files.

Sometimes I notice that its CPU usage is exorbitant during these tasks, although this is not the case all the time. At worst it can use close to 100% of a 2.8GHz P4.

Tags: patch
Revision history for this message
Frederic Jacquot (frederic-jacquot) wrote :

I noticed Easytag is getting slower as the journal fills up. Emptying the journal regularly helps to keep decent performances.

Revision history for this message
Jerome COUDERC (easytag) wrote : Re: [Bug 129482] Re: easytag is very very slow

This problem was fixed at least in the version 2.1.3

Frederic Jacquot wrote, the 19/02/2008 01:55 :
> I noticed Easytag is getting slower as the journal fills up. Emptying
> the journal regularly helps to keep decent performances.
>
>

Revision history for this message
Hew (hew) wrote :

This issue has not been fixed, as I experience it with easytag 2.1.4-1 in Ubuntu Hardy. It's taking 2-3s per file, just to change a tag. The CPU usage is 100% on one core at all times during this process. My system specs are not the issue (Core 2 Duo, etc). I'm using XFS.

Changed in easytag:
status: New → Confirmed
Hew (hew)
Changed in easytag:
importance: Undecided → Medium
Revision history for this message
Joul (julian-endres) wrote :

Hey,
recently I tried easytag 2.1.6 with kubuntu gutsy and I noticed the same bug. It took over 2hours renaming about 2.000 songs with a Celeron 1,6GHz.
As described by Hew McLachlan it takes 2-3s per file. But is it really an issue of easytag? I don't think this problem appears on other linux distributions!?

Revision history for this message
Ville Ranki (ville-ranki) wrote :

Looks like it does some heavy processing in UI thread, as the whole UI is frozen when applying tags. Things like this should be done in background so that UI stays usable.

Revision history for this message
jaco salvi (jaco-salvi-gmail) wrote :

Looks to me like EasyTag does a reload or refresh of the entire list of files after saving a change to one file. This explains why the time-per-file grows with the number of files in the list.
I'm on 2.1.6 compiled 14 Nov 2009 and the problem is still there.

Revision history for this message
Mark Jones (linuxguy2009-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

I just tried Ex Falso to test the claims I see here. I've always used Easy-Tag before.
Copied 500 random AAC tracks to a desktop folder.

Easy-Tag processed all 500 in 5 minutes.
Ex Falso processed all 500 in 5 seconds flat.

Yes I would agree something is wrong when it takes 60 times longer to complete the same task!

Revision history for this message
Xavier Neys (xavier-neys) wrote :

Just like Jaco Salvi wrote. I launched a mass fix (no idea what it wants to fix btw) 16 hours ago on 12500 tracks and easytag 2.1.6 is still busy on a 3.0Ghz quad-code system. It obviously refreshes the entire list after every fix.

Revision history for this message
pcix (roma-zharkov) wrote :

There are too many updates in UI during batch editing.
Simple commenting out some of them (status bar, for ex.) leads to faster processing.
Freezing of the entire UI using the same method shows amazing speed value.

Hew (hew)
Changed in easytag (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
zasran (erik-zasran) wrote :

In addition to what other said the list of files keeps updating even when just going from file to file (pg-up/pg-down), it takes forever to just go from file to file. The width of various columns number of times everytime I press pg-up or pg-down. This might depend on width of various elements (i.e. not sure if it happens always).

Revision history for this message
K1773R (k1773r) wrote :

@pcix how did you manage to freeze the UI while saving files?
easytag is really good but the UI "flood" is making it unusuable for alot of files.
do you still have the source or a patch file? :)

greetings

Revision history for this message
Samuel S. Gross (ssgross) wrote :

Hi. Using Easytag 2.1.7 in Arch. 13,700 files takes 7sec. per file to rename with a quad core i7. I think this is unacceptable to continue to update this program without addressing this bug. It was present 4 years ago when I used ubuntu, and has always been a bother. It is a shame because easy tag is, in my opinion, the best program out there for managing a music database. why is so hard to fix - freeze the window during saving, and don't update it until the save completes.

Revision history for this message
Matteo Croce (teknoraver) wrote :

IThe bug was fixed upstream, this is the patch

Changed in easytag (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "speed.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Hew (hew)
Changed in easytag (Ubuntu):
status: Fix Committed → Triaged
Changed in easytag:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in easytag:
status: Confirmed → Expired
Revision history for this message
Matteo Croce (teknoraver) wrote :

Fixed in upstream 2.1.8, pleas update the package

Changed in easytag (Ubuntu):
status: Triaged → Confirmed
Changed in easytag (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
clickwir (clickwir) wrote :

Can we please get a newer version of this. EasyTag released 2.1.8 on 2013-2-10.

I'm updating 1300 files, it's on 295 after 15 minutes. I can walk away for a while, but this redrawing of the entire list after almost any action just makes this a large chore.

Revision history for this message
Xavier Neys (xavier-neys) wrote :

2.1.8 fixes this issue. But beware that a severe regression affects 2.1.8: if passed a file name or directory name, easytag will jump to / and then read the whole tree (or try to and hang) if the read subdir automatically option is on.
See https://bugzilla.gnome.org/show_bug.cgi?id=693613
The speed-up is great but this bug is a real showstopper.

dobey ppa and debian's package from http://packages.debian.org/sid/amd64/easytag/download are affected.

Revision history for this message
James Cowgill (jcowgill) wrote :

Was fixed in 2.1.8-1 (trusty)

Changed in easytag (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
ggallozz (ggallozz-gmail) wrote :

I think is not fixed: 2.1.10 is still very slow to load a specific directory (72 MP3 files), with NO SCAN SUBDIR set.
My system summary is here http://pastebin.com/7rqt9Caj

Revision history for this message
ggallozz (ggallozz-gmail) wrote :

I think is not fixed... suite

since I've posted the previous commend, Easytag didn't finished scanning that directory yet ....

Revision history for this message
James Cowgill (jcowgill) wrote :

Hi ggallozz

This bug is about slowness during tagging, but it sounds you're getting slowness when searching directories. Can you see if it affects 2.2.4 (it's in vevet)? Does it affect another directory with roughly the same number of files? Is the directory strange in any way? If there is a bug, can you open a new bug and I'll look at it in a few days when I'm back at my main computer.

James

Revision history for this message
Matteo Croce (teknoraver) wrote :

It's extremely slow in 2.2.2

Revision history for this message
piattj (troodonic) wrote :

Absurdly slow, unusable in 2.4.3. Uninstalling... Too bad it was my favorite.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.