On Wed, Jun 25, 2025 at 08:57:42PM -0700, 1...@110110.net wrote:
>
> I personally would like debian to research a version of debian for
> high performance computers, or at least a fork of debian optimized
> for high performance computers; ready to occupy large sets of ram,
> hd space, and completely utilize new technology in x86 family
> processors Made after 2020 or so; where large sets of ram (64gb+)
> can just be occupied up to 35% for performance reason, such as
> caching and hopefully occupy high performance code
It's not clear what problem you are trying to solve here. First of
all, just because you have a huge amount of memory doesn't mean that
*using* extra memory is a good thing.
For example, if you have a hundred processes all using the GNU C
library, sharing it not only (a) saves memory, but also (b) can speed
performance because the pages may already be in memory and so don't
need to be loaded from disk, (c) can speed performance because the
parts of the shared library might be in the CPU cache, and (d) when
there is a security vulnerability, updating the shared library fixes
all of the programs that use that shared library, where as if you use
static linking, someone has to recompile all of the programs using
that library, upload them to the Debian package archive, and then
everyone has download all of those packages.
The main disadcvantage of using shared libraries is that the upstream
developers have to be careful; about maintaining ABI backwards
compatibility, which seems to be a lost art amonsg newer, more
"hipper" languages such as Go and Rust, who have completely given up
on this. But for people who can be careful, the advantages to their
users can be huge.
- Ted
