SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi!!
i'm having some problem with slackware 12 here. the problem is that under cpu intensive operations, the system just slows down
for example, if I try to compile a huge program, or play some game, it'll *REALLY* slow down at some point. that's strange, i've beem using slackware since 98 or 99 and it never happened. it don't matter what WM I use. I tried xfce and gsb gnome, and it slows down with both. actually, if I use just plain text terminal and try to compile something big, it slows down too.
this happens with both the default slackware kernel or the newers, that I compile sometimes. now i'm using 2.6.14 and the problem goes on.
does anyone know what may the cause be, or have anyone ran into this issue?
Regards
ok now that's very strange. on my mother's machine I installed ubuntu. and, gee, it's a hell faster than slackware huh
but I noticed a difference: on the system monitor applet for gnome, i enabled on both machines the processor graph. it shows some graphics, the most important here being USER, SYSTEM and NICE. well, the problem is that my slackware's NICE is almost always at the top, maybe explaining the slowdown. but what does it mean? i do know the nice program, but what the nice graphic mean? the ubuntu's nice is always veeeeeery low, actually i couldn't see it by now.
the LOAD graphic is always high on slackware too.
just a detail: the ubuntu's machine is something about 4 times slower than my slackware box.
can someone help me?
ok some more info. the NICE graph says that the processor is occupiead with niced programs
Quote:
excerpt from 'man nice'
NICE(1) User Commands NICE(1)
NAME
nice - run a program with modified scheduling priority
SYNOPSIS
nice [OPTION] [COMMAND [ARG]...]
DESCRIPTION
Run COMMAND with an adjusted niceness, which affects process schedul-
ing. With no COMMAND, print the current niceness. Nicenesses range
from -20 (most favorable scheduling) to 19 (least favorable).
-n, --adjustment=N
add integer N to the niceness (default 10)
ok, i was mistaken. it's not that niced processes are occuping the cpu. it was the tracker daemon. after disabling it, i got the real behavior: after heavy duty like games or compiling sources, slackware gets veeeery slow. from here on, any process will take a helluva time to make something. even a music player gets 100% cpu!! it's just as if the process scheduling went crazy!! if I close everything, the cpu stays idle. if I open terminal for instance, 100%=S that's why the tracker daemon, which is niced 19, was taking the whole processor.
i would like to believe it was some misconfiguration i did in the kernel, but even the default kernel will have this flaw. I also noticed some more ppl have this problem, but after googling, i could not find any answer yet.
I didn't nice anything, I'm using an almost vanilla slacware with GSB. just to remeber, the problem was always there, even before GSB. the niced program was trackerd, that was niced 19, and some services kernel related, as kthreadd, ksoftirqd/0, events/0, khelper, kblockd/0, kacpid, kacpi_notify, kseriod among others, which was nice -5.
i don't know what it could be...
hi!!
i'm having some problem with slackware 12 here. the problem is that under cpu intensive operations, the system just slows down
for example, if I try to compile a huge program, or play some game, it'll *REALLY* slow down at some point. that's strange, i've beem using slackware since 98 or 99 and it never happened. it don't matter what WM I use. I tried xfce and gsb gnome, and it slows down with both. actually, if I use just plain text terminal and try to compile something big, it slows down too.
this happens with both the default slackware kernel or the newers, that I compile sometimes. now i'm using 2.6.14 and the problem goes on.
does anyone know what may the cause be, or have anyone ran into this issue?
Regards
You should also consider that this problem might be memory related instead of CPU related. Try issuing cat /proc/swaps before and after one of your slowdowns to see if you are swapping excessively during a slowdown.
You should also consider that this problem might be memory related instead of CPU related. Try issuing cat /proc/swaps before and after one of your slowdowns to see if you are swapping excessively during a slowdown.
-------------------
Steve Stites
well, I don't believe it's a swapping problem, since there's no hard disk activity (unless when I ask for it) during slowdown.here it goes.
before slowdown
Code:
[alisson@northstar:~]$ cat /proc/swaps
Filename Type Size Used Priority
/dev/hda2 partition 506036 0 -1
during slowdown
Code:
[alisson@northstar:~]$ cat /proc/swaps
Filename Type Size Used Priority
/dev/hda2 partition 506036 0 -1
no, I didn't paste it wrong. they're both the same
also, here's free output during slowdown
just noticed one thing: I have a 500MB swap partition that's never used.
its priority is also set to negative numbers (see previous output of cat /proc/swaps). and if you take a look at swapon manpage, you'll notice that priority is a value between 0 and 32767.
if I turn off and on again the swap, its priority will get even lower:S
maybe this is messing some kernel swap algorithm, and this is introducing the latency... don't know, just guessing...
i tried mkswap /dev/hda2 again, but no sucess, i still can't use the swap, even when using 100% physical memory
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.