On 10/09/2016 10:09 AM, Carlos E. R. wrote:
On 2016-10-09 16:05, Anton Aylward wrote:
On 10/09/2016 09:08 AM, Carlos E. R. wrote:
On 2016-10-09 14:35, Anton Aylward wrote:
Your SYSTEM
What get installed, what comes from the main repositories and updates and Packman.
I don't know. Because the data files I work with I want to be loaded fast, too.
I'm not arguing with that. I've made the case elsewhere, repeated so, that given enough memory to avoid code paging/swapping, that the RSS is adequate (often barbecue of good module design and a good link editor) that data, because it's streaming or if, for example, the sidecar files have to be sync'd often without disrupting the workflow, that a high speed DATA partition makes more sense than high speed OS. After all, the code-base is often stable. I run up the OS;/ Usually I turn the machine on while on the way to the bathroom when I wake so how fast it boots isn't critical. When I'm up and running I have a few long lived programs, the X server, a xterm, Thunderbird, Firefox. I have enough memory that the core code-base for those forms the RSS. Its the data that takes up 'dynamic' & pageable memory pages, and even then Thunderbird and Firefox are network programs, they just need space to do their rendering. Most of their demand goes to the OS for network services. So what's the breakdown of my disk? * The RootFS I chose to include /usr but not /boot * /boot * /usr share I separated this out thinking that one day I'd NFS share this ... So I have df -h / /boot /usr /usr/share Filesystem Size Used Avail Use% Mounted on /dev/mapper/vgmain-vROOT 20G 8.8G 11G 45% / /dev/sda1 1.9G 299M 1.5G 17% /boot /dev/mapper/vgmain-vROOT 20G 8.8G 11G 45% / /dev/mapper/vgmain-vUsrShare 5.0G 2.4G 2.7G 47% /usr/share So I could put that part of my SYSTEM on a 32G flash card or something that is not 'rotating rust'. Low latency. For the most part its not something that gets written to ... much. I then have * /home Of course. And there are a number of mounted FS under ~anton for movies, photographs, music and books * /usr/local so that it can survive updates :-) * /srv That's where all the web stuff lives * /opt I treat that rather like /usr/local but its a bit more 'experimental whereas /usr/local is serious, ling term installs with proper libraries and documentation * /tmp If I had a 120G or larger SSD I would have no hesitation about putting /tmp there and making more use of memory based 'tmpfs', perhaps for some of the caches. I might even rearrange /home/anton so a few more things were in separately manageable FS and put /home on the SSD. The point I'm trying to make here is that the really big stuff I have is manageable because its on a separate file system from the SYSTEM. I could have an enormousness set of movies, music, video, web site material and it isn't on the same FS as the SYSTEM. As it stands, even the things that are ENORMOUS on my system, mainly the ~/Photographs tree, is partitioned in a way to ease archiving and backup. I could, for example, free up a lot of space by off-lining everything before say, 2015. its still out there on generational DVDs. Similarly the email I chose to archive, which isn't a lot, comparatively speaking, but does add up over the years. But data is not SYSTEM As someone once said, "Code is Code and Data is Data and ne'er the twain should meet". Well, yes. there /etc and all the config stuff that can be viewed a 'data'. But config is tightly coupled with code whereas real data isn't. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org