Liste des Groupes | Revenir à col advocacy |
On Fri, 3/28/2025 5:25 PM, Lawrence D'Oliveiro wrote:Linux can use memory for filesystem cache that can be quickly dumpedI don't know if the message is getting through yet,
and reallocated for regular application use. This is why the memory
display distinguishes between “free” memory and “available” memory --
the latter includes both free memory and cache space.
Windows isn’t so good at this, let’s face it.
but Windows has every feature Linux has.
Why do you think they hired
7000 developers ? They're running Xerox machines all day long. the task
bar descends just like MacOS. What a coincidence.
Windows has System Read cache and System Write cache.
It has System Read cache in Win2K. System Write cache came later.
The System Read cache is like every other implementation.
Unix had it, MacOS had it (on my G4 in 10.3), Linux has it,
Windows has it (since Win2K at least). At the time this happened, all
the OS companies were running their Xerox machines and copying shit from
one another. In all of them,
memory is not booked, and as Frank would note, "memory is to be used",
and the ideal case happens with System Read caches, on all systems. They
give the memory back, any time you need it.
System Write caches are booked. And they have percentage limits on how
much memory they will book. System Write caches are a non-ideal case,
and if you're good, you can "jam" an OS such that it freezes. I managed
to do that once, realized the mistake I'd made, but I couldn't type fast
enough to stop it :-/ OS froze. Had to reboot.
Use a little imagination please. Come out of your cave.
Paul
Les messages affichés proviennent d'usenet.