On 13 Oct 2003, at 10:43 am, Christian Herzyk wrote:
Stroller wrote:
on 11 Oct 2003, at 9:58 pm, Jerry McBride wrote:
There used to be tremendous performance gains by running prelink across ones
KDE installation... but since KDE 3.1.x... the programming efforts of the KDE
team really shines and prelinking isn't all that necessary any more.

Gaaa! I just emerged KDE 3.1.4 the other day & it's sill slow as sin on my little PII 400 laptop with only 64meg..!
I'd really like it to be faster, as it's my favorite Linux environment - none of the screenshots I've seen of lightweight WMs appeal to me.


I'm recompiling glibc with prelinking support at the moment - I think I'm then likely to have to recompile all my libraries before prelink will work. Is it worth the effort..? I think I've got to try, now I've started.

Stroller.

What do you expect form your machine? The CPU is by now quite old, but should be able to manage KDE quite fine though.
The problem is your RAM. With 64MB your RAM will probably be filled with the usual linux stuff and KDE. I guess even without starting anything else your laptop will have to start swapping things out.
I tried to run Knoppix (OK I know it need more RAM) on a PC quite similar to your setup and it was REALLY slow (around 5 minutes startup time)
Adding 128MB of RAM helped a lot though. I recommend you do the same if you want to continue using KDE.

Perhaps you're right that I have unreasonable expectations of this machine - I've never had a machine with so little memory before (or at least, not since I upgraded from my first Pentium 150 which had 32meg). My expectations were that, as a Pentium II it should be adequate & that KDE should "just work" - right now it's unusable.


Unfortunately the cost of memory for these little Vaios is quite prohibitive - after about 45 minutes Googling I've managed to find a UK supplier - he wants �120 for an additional 64meg (the maximum this machine will take).

I'll have to ponder further whether that's a good investment.

Stroller.


-- [EMAIL PROTECTED] mailing list



Reply via email to