On Wed, May 22, 2002 at 08:59:45PM +0200, Marc-Christian Petersen wrote:
> and again, i think, i am the first man, beneath you, who tests this
> version :)
Yes, I guess so. It's great to know there are some people besides me
testing the patch :-)
> This code went into WOLK 3.4 Final version. I've tested it, runs
> fine till now. And i must say, my System is running very very smooth
> with Compressed Cache activated :) ...
What's your system configuration? Do you have page cache support
enabled? What's the size you are setting to the compressed cache?
> and even much smoother with Lock-Break from Preemptible
> Kernel. version 0.23pre4 seems to work fine with it, prior versions
> freezes my mashine.
So doesn't it freeze with Lock-Break when untarring a kernel any
longer? Even with page cache support enabled?
> A question for understanding: What should be the Size of Compressed
> Cache? Is there a way to calculate it by hand if, let us say, RAM is
> 256MB and also SWAP is 256MB?
I don't think there will have one optimal compressed cache size during
all the time your system is up. That's because your system will have
various memory needs and memory references throughout this time and a
single compressed cache size is unlikely to be the optimal for all
these scenarios.
Anyway, while we don't have adaptivity working reasonably well for
compressed cache, you have to pick a size to be able to have
compressed cache benefits (hopefully) by now. I would choose something
like 15% to 25% of your memory size, because you wouldn't have too
much aditional cost since it's not that large and also it isn't so
small that can still provide some benefit, if that's the case. That
way, in your case, I would set the compressed cache size to something
like 40Mb and 64Mb.
> Hint: You should readd config help that the size is still tuneable
> via /proc, not only with adding a boot param to the bootmanager :)
Nice tip, I will do that.
> Thanks for your great work Rodrigo. If you need help, let me know!
Thanks for your help.
Best regards,
--
Rodrigo S. de Castro <rc...@im...>
|
