On 2025-07-24, Javier Martinez wrote:
El 24/7/25 a las 18:07, Nuno Silva escribió:
On 2025-07-24, Javier Martinez wrote:
El 24/7/25 a las 16:43, Rahul Sandhu escribió:
Hi Dale,
That's the biggest reason I have portage's work directory on tmpfs. If >>>>> I start having to do it on a disk because of a lack of memory, I'll do >>>>> it on spinning rust to save my m.2 stick.
This really isn't all that true these days, please take a look at the
Gentoo wiki article for Portage TMPDIR on tmpfs, which states[1]:
Users are strongly cautioned against buying additional RAM to use as tmpfs.
[1] https://wiki.gentoo.org/wiki/Portage_TMPDIR_on_tmpfs
Regards,
Rahul
Its not question of thuth if not opinions instead, and neither to buy
more RAM modules but to take a computer with enough RAM from the
beginning (I will try the next one having 64 GB).
I don't have swap on disk. And got a system with 32 gb of RAM. I
dedicate 16 of them to /var/tmp/portage. My PC could die and the
harddisk still alive to be used in another system (such as rockpi4c+)
If you don't use RAM as tmpfs maybe your harddisk will live 5 years,
if it's almost full don't so many years according of the TBW of each
hardisk.
I think hard drives tend to usually last way longer than that, including
those used on Gentoo systems and which house /var/tmp/portage.
So, is not buy more RAM, is question to get from the beginning enough
RAM to be able to protect your SSD disk. You can also put your
distfiles dir in tmpfs use --jobs 1 and got it to remove it after
emerging.
Less writtings more lifespan and gentoo does so many writes when
emerging.
Maybe a separate on-disk filesystem with very lazy writeback is a more
appropriate solution for this?
How many RAM modules have you broken in your life by excessive use? I
did not break any yet, hard disks a lot
Why are you assign /tmp or /run a tmpfs directory? is a no sense for me.
Data that would not be keeped between reboots should not be written to
a disk which dies slowly with each byte-written
If you have /tmp in RAM is a no sense to defend /var/tmp/portage in
disk. I agree that you SHALL NOT buy RAM expansions to your PC to do
it as it can be cheaper one m2 hard disk. But if you have RAM use RAM
and protect your disks.
There have certainly been times when buying RAM wasn't really
financially worth it compared to just buying more hard disk space. That
*may* now change if RAM is sufficiently cheaper, and for systems where
RAM modules are easily available, given that several hard disk
manufacturers are replacing the more affordable hard disk tiers with
SMR-only offerings, meaning the price tag for "CMR" disks ends up being
higher.
There have also been times when the motherboard simply could not take
more RAM. I have one amd64 system where I can't use more than
3-something GiB - chipset limitation on the address space puts the
maximum at 4 GiB, and on top of that it still has to include the PCI
hole. (Thanks, Intel!)
(You do understand that if /var/tmp/portage is in disk, then it is
*also* in RAM?)
--
Nuno Silva
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)