Today's crappy piece of crap is Yumex, a remarkably bloated and sluggish graphical front-end to Yum, written in (sad to say) Python. It's using 97MB of memory and 20% CPU and not, so far as I can tell, doing a goddamn thing.

And that's once I managed to actually get it to run (I almost said "work", but I have no sign of that); for hours it was complaining that something else had locked yum and wouldn't run at all.

I tried running it using X over SSH - locally - and sshd was chewing up 40% of my CPU.

I swear that Fedora Core 4 didn't suck this bad.

Update: OKay, I'll give it some credit. If you wait the fifteen minutes or so it takes to start up, and put up with its wallowing GUI, it will actually let you browse packages and install them.

Just.

Very.

Slowly.

Update: God, this thing is just excruciating. It's using 177MB of memory now - resident. I tried the category view. Clicked on Applications, and then on Educational Software. Nothing happened for a couple of minutes (but the CPU was very busy). Then, nothing continued to happen, although now the application responded to mouse clicks.

Then I found out that in the category view, it divides packages into Mandatory, Default, and Optional. It defaults to Mandatory, and since there are no mandatory educational applications, it didn't show anything.

There's no indication that it's busy - other than the fact that it locks up.

There's no All tab.

I clicked on the Engineering and Scientific category a few minutes ago, and it's still frozen. Okay, so that bloody beagle-build-index thing is still running (620 minutes of CPU time now). Okay, so I'm running under VMWare with only 400MB of memory allocated. I expect it to be a little slow; that's part of the reason I set it up this way. I want performance problems in my code to be obvious so that I can catch them early.

I wish someone had taken the same approach for yumex, because it is pure, distilled suck.

Posted by: Pixy Misa at 01:31 AM | Comments (35) | Add Comment | Trackbacks (Suck)