Russ Tremain writes:
>
> At 4:48 PM -0800 1/24/01, Brian Behlendorf wrote:
> >
> >I recommend mounting /tmp on some sort of memory-based filesystem for
> >maximum performance - this made a big difference on apache.org.
>
> thanks.. this is the next step; unfortunately, have to upgrade
> memory first.
>
> Also, hard to know how big to make this device; I'm planning on
> 1 GB, and then writing a cron job to clean up left-over server
> tmp dirs.
There shouldn't be any left-over server directories unless the server
crashes or encounters a serious error. Is this just general caution, or
have you had an actual problem with left-over directories?
A good alternative to the memory based filesystem is a disk based
filesystem that supports soft updates (even better than a virtual memory
based filesystem, not quite as good as a physical memory based
filesystem but a much more efficient use of resources). If neither of
those are viable alternatives, you can at least mount /tmp asynchronous
if your system supports it, although that pretty-much means that you
have to recreate it on reboot rather than just fsck-ing it.
-Larry Jones
There's a connection here, I just know it. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
