DragonFly BSD
DragonFly users List (threaded) for 2004-11
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Symlinking /home and /tmp with bsdinstaller to save space

From: "George Georgalis" <george@xxxxxxxxx>
Date: Wed, 24 Nov 2004 17:16:11 -0500

On Wed, Nov 24, 2004 at 10:34:39PM +0100, Simon 'corecode' Schubert wrote:
>On Wednesday, 24. November 2004 22:11, George Georgalis wrote:
>> >> /
>> >> swap
>> >> /var
>> >> /usr
>> >>
>> >> then symlink
>> >>
>> >> /var/tmp
>> >
>> >This ought to be on permanent storage.
>> Yes, I generally don't put any partitions in a memory filesystem.
>> There may be specialty applications where it would be desirable.
>> And indeed, I do sometimes mount a temporary ram filesystem, for
>> archive extraction/build. That can be a lot quicker then extracting
>> and writing on one disk, but I nuke the memory filesystem when done
>> because how much available ram helps a running system performance.
>i don't think there is much of a difference whether the system swaps 
>out/flushes data of a memory filesystem or cached data of a "real" 
>filesystem... except, of course, that a memfs eats swap

really? I have a box fast enough to make a difference, 1Ghz, that I
may get be able to benchmark out of tonight. I'll time extraction
and default build, in both mfs and ufs, of something big enough to
make a difference. Linux kernel is about ~30Mb compressed, any other

My reasoning is simply that the ide channel is being used to read the
archive, the extracted data is memory before it goes back down the
ide channel to disk, the bottleneck is the disk interface. Maybe soft
updates will work better than I expect?

// George

George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@xxxxxxxxx

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]