Re: LVM root?
Lennart Sorensen <lsorense@csclub.uwaterloo.ca> writes:
> On Wed, Oct 11, 2006 at 07:55:07AM -0400, dtutty@porchlight.ca wrote:
>> Isn't there a performance hit doing this? If a programme is putting stuff
>> in /tmp to otherwise reduce its memory footprint, does it make sense to
>> circumvent that and put /tmp back in memory? If a program is accessing
Older programms have odd defaults for what is too big of a memory
foodprint. Like sort starting to use tempfiles at 1MB. Compared to a
browser using 500MB that is laughable. So a lot of the time it is
perfectly fine to keep the tempfiles in ram. And if not then it swaps
them.
>> both its /tmp file and another working file, with /tmp effectivly in
>> swap, one has no controll over which spindle that page is on (assuming
>> more than one disk) whereas if /tmp and /var/tmp are on a different
>> spindle from the working directory they could be accessed at the same
>> time.
Then put your swap on a differen spindle from your working directory. :)
>> I wouldn't want to use /tmp for a temporary iso file. If I get the iso
>> created and then have a power failure, I don't want it gone when
>> rebooting cleans out /tmp. I thought that's what /var/tmp is for.
Change your nautilus tmp dir to something more permanent then.
>> Disk space is cheap. Other than saving space in /tmp when its not
>> needed, is there an advantage to having it use tmpfs instead of a
>> 'normal' device (partition, LV, whatever)?
Could be faster. Never measured it. Saving that extra partition or LV
was always good enough a reason for me.
Another reason is that tmpfs can never fail the fsck on boot or
otherwise become a corrupted filesystem and cause troubles on
boot. You get an instant fresh one every time. And you can't get I/O
errors from a broken disk.
> /var/tmp is for things you do NOT want to loose on a reboot, but which
> are otherwise still temporary files. /tmp is for stuff that you really
> don't care about, and which a reboot should remove (I know there used to
> be a setting in debian that would clean /tmp on boot automatically).
> For generating CD images I think I would use my home dir or some other
> data storage location which makes sense for working on large files.
> /tmp isn't it and never was.
I always pipe the data directly to the burner. growisofs does it by
default. No temporary iso to create, waste of time. Nautilus should
realy do that too.
But even so, my /tmp is limited to 1G currently so creating an CD iso
in there is no problem. With 2G ram it probably wouldn't even swap
anything if I don't have galeon running.
MfG
Goswin
Reply to: