LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Sluggish performance with Slackware64 14.0 (http://www.linuxquestions.org/questions/slackware-14/sluggish-performance-with-slackware64-14-0-a-4175438918/)

dimm0k 11-27-2012 10:04 AM

Sluggish performance with Slackware64 14.0
 
I've upgraded from Slackware64 13.37 to 14.0 and while everything was good in the previous version, 14.0 seems a bit more sluggish than usual. As user, Midnight Commander would load up instantly on 13.37. With 14.0 however, it takes a good 5+ seconds after issuing the command before Midnight Commander actually starts up. I've tried wiping out the config file for mc in ~/.config/mc, but no change.

Also last night as I wanted to change folders within KMail it took maybe 8+ seconds before it successfully moved from the current folder to the one I clicked on. During that waiting stage KMail looked like it had locked up as it wouldn't do anything.

Anyone else witnessing this or have any suggestions?

KeithE 11-27-2012 10:29 AM

Re: Sluggish performance with Slackware64 14.0
 
How much RAM and what processor do you have? I found that, on my very-low-end 64-bit Zotac ZBox and Acer Revo 1610 nettops with 2 Gb and 1 Gb RAM respectively, 32-bit Slackware 14 was much faster than 64-bit Slackware 14. This was especially true when running XFCE (KDE was too slow to bother with on both boxes).

H_TeXMeX_H 11-27-2012 11:26 AM

I have benchmarked both versions and 14.0 is at least as fast as 13.37 and sometimes faster (encryption).

dimm0k 11-27-2012 07:55 PM

I just switched to kernel 3.6.8 and was hoping that this sluggishness was isolated to just the user, but I tried running Midnight Commander as root and timed it. Took roughly twelve seconds from the time I pressed Enter to seeing the mc screen. My system is a notebook with 16GB of RAM and the i7-2720QM CPU, which I'm sure is more than enough to handle Midnight Commander. KDE's KMail looks to be okay again either due to the new kernel or fresh boot. I'll keep an eye out on that, but mc loading that slow is kind of annoying. Is this normal or am I only noticing it now?

Woodsman 11-27-2012 09:25 PM

Quote:

I tried running Midnight Commander as root and timed it. Took roughly twelve seconds from the time I pressed Enter to seeing the mc screen.
This might be two different problems. I noticed on my systems that mc is opening slower than previous Slackware releases. I haven't run any actual stop watch tests. I should investigate further. I'm only adding that if we both are seeing mc open slower then using mc might not be a good barometer of overall system performance.

dimm0k 11-27-2012 11:15 PM

Not sure if this is related to mc opening slow, but in google-chrome when I attempt to download something the dialog that usually opens after clicking the link has a delay as well. The dialog itself has no delay opening, but listing the download directory's contents takes a good 3-4 seconds before listing so in the meantime I can't do anything until it's listed. I'm not sure if I'm seeing any negatives in overall system performance, just these few exceptions like mc and google-chrome. KMail previously as well, but it looks okay now for the time being.

kingbeowulf 11-28-2012 02:59 AM

mc pops up in a blink, here. 14.0 is way faster on this box than 13.37 (same hardware). Slackware14 stock + multilib, clean install.

I see this query a lot: "Why is version X slower than older version Y?" Unfortunately, I have never experienced this issue with Slackware. Except for jumping ship for SLAMD164 11 to 12.2 (I was weak for the x86_64 siren song...), Slackware always run as good or better with each release. I do not run the latest and greatest hardware.

There could be a number of reasons for sluggishess; I give a high probability to PEBKAC as the culprit. Also: check your SAMBA and/or NFS settings. Do you have a USB drive attached that has to spin up?

dimm0k 11-28-2012 09:42 PM

Quote:

Originally Posted by kingbeowulf (Post 4838559)
mc pops up in a blink, here. 14.0 is way faster on this box than 13.37 (same hardware). Slackware14 stock + multilib, clean install.

I see this query a lot: "Why is version X slower than older version Y?" Unfortunately, I have never experienced this issue with Slackware. Except for jumping ship for SLAMD164 11 to 12.2 (I was weak for the x86_64 siren song...), Slackware always run as good or better with each release. I do not run the latest and greatest hardware.

There could be a number of reasons for sluggishess; I give a high probability to PEBKAC as the culprit. Also: check your SAMBA and/or NFS settings. Do you have a USB drive attached that has to spin up?

I've disabled SAMBA, as well as NFS and still the same issue. I have tried booting off the Slackware DVD, installing the necessary packages (aaa_elflibs and mc) to test it from there and it looks fine from there... looks like it could be something with my system that's causing the delays =( One other thing to rule out is I'm using kernel 3.6.8, while the Slackware DVD uses 3.2.29... will test that out and report back.

EDIT: tried the stock 3.2.29 kernel and still no go... anyone have any suggestions other than wiping the system and starting from scratch?

SqdnGuns 11-28-2012 10:27 PM

Have you run memtest or test your HDD?

dimm0k 11-29-2012 02:21 PM

Quote:

Originally Posted by SqdnGuns (Post 4839181)
Have you run memtest or test your HDD?

In my opinion it's too isolated to be a memory or HDD issue... if it were, I would be experiencing odd behavior elsewhere as well, possibly even machine lockups. Since I've upgraded from 13.1 to 13.37 to 14.0 I've decided to just backup my configs and just install 14.0 from scratch. Probably not the best approach to solve an issue, but it does feel better that I'm on a clean system anyway. I suspect it had something to do with either a corrupt or conflicting dependency because currently mc loads up snappily after the clean install and this is using my previous config files. Should this issue arise again as I put my system back together from the wipe I'll update this thread in case anyone else comes across this.

Martinus2u 11-29-2012 03:04 PM

maybe an strace with time stamps to see where the time is lost? May need a 13.37 measurement for comparison.

Old_Fogie 11-29-2012 05:17 PM

Midnight commander has a long outstanding wierdness (not a bug) if you didn't address/fix/or omit ipv6 correctly in your /etc/hosts file.

Woodsman 11-29-2012 06:26 PM

In etc/hosts? How?

fatalfrrog 11-29-2012 07:28 PM

mc might be hanging on trying to resolve your hostname (I think there's another thread around here talking about it). Add your hostname to the localhost address.
In any case, I'm sure strace will show you what's up!

dimm0k 12-01-2012 09:39 AM

Ok, so with the help of strace I've narrowed down the culprit! It looks like something in my /etc/rc.d/rc.firewall (using iptables) is causing the long delay... with the firewall turned off, mc starts up nice and fast. As soon as I turn it back on the delay occurs. From the looks of strace, I'm not sure why mc is making ANY attempts to contact my router's address... here's a snippet of strace

Code:

munmap(0x7f4fc77b7000, 4096)            = 0
socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.1.1")}, 16) = 0
poll([{fd=3, events=POLLOUT}], 1, 0)    = 1 ([{fd=3, revents=POLLOUT}])
sendto(3, "\3\254\1\0\0\1\0\0\0\0\0\0\4ETH0\4home\0\0\1\0\1", 27, MSG_NOSIGNAL, NULL, 0) = 27
poll([{fd=3, events=POLLIN}], 1, 5000)  = 1 ([{fd=3, revents=POLLIN}])
ioctl(3, FIONREAD, [66])                = 0
recvfrom(3, "\3\254\205\203\0\1\0\0\0\1\0\0\4ETH0\4home\0\0\1\0\1\300\21\0\6\0"..., 1024, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.1.1")}, [16]) = 66
close(3)                                = 0
socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.1.1")}, 16) = 0
poll([{fd=3, events=POLLOUT}], 1, 0)    = 1 ([{fd=3, revents=POLLOUT}])
sendto(3, "\312\203\1\0\0\1\0\0\0\0\0\0\4ETH0\0\0\1\0\1", 22, MSG_NOSIGNAL, NULL, 0) = 22
poll([{fd=3, events=POLLIN}], 1, 5000)  = 1 ([{fd=3, revents=POLLIN}])
ioctl(3, FIONREAD, [22])                = 0
recvfrom(3, "\312\203\201\2\0\1\0\0\0\0\0\0\4ETH0\0\0\1\0\1", 1024, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.1.1")}, [16]) = 22
close(3)                                = 0

if anyone knows what's going on or need more from strace, let me know. In the meantime I'm going to see if I can pinpoint where in my firewall it's stopping at...


All times are GMT -5. The time now is 07:59 AM.