On 01/26/2014 06:04 PM, Carlos E. R. wrote:
On 2014-01-26 23:50, Peter wrote:
Does it make any difference in your opinion to have /tmp on a separate partition on an SSD rather than lumping everything in with / ?
Having it all on the same partition spreads writes over the disk, instead of concentrating them on a smaller area. So yes, a single partition for all is better in that respect. IMO.
I disagree with that for a couple of reasons. First, it makes some presumptions about the SSD. A SSD is not like a normal disk, a 'passive' device. In effect it is a storage management device; there is an intelligent agent running there which manages the resource. How it does that is going to be different for different vendors and I expect for different models. Even of it it was a linear passive device the type of file system used is going to have a lot to do with the 'spread'. Taking this further, if the disk is 'partitioned' with LVM rather than the tradition tools then the allocation strategy is within the VolumeGroup, not simply extents, and can be spread out over the drive. (Yes I know you can use the 'continuous' flag to override that.) My point here is that "It All Depends" - Context is Everything. BtrFS, such as the single partition I am running experimentally on my 20G drive, can occupy an entire data storage device and replace the MBR or GPT partitioning schemes. It has has 'subvolumes' that appear like partitions, they appear as mount points at least logically, but you can't use different files systems :-) I'm not sure if those subvolumes have meaningful and effective noexec,nosuid, nodev options. https://btrfs.wiki.kernel.org/index.php/FAQ#What_does_.22balance.22_do.3F -- shin (n): A device for finding furniture in the dark. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org