4 ms·

Except Xcode can't possibly know before hand when I do need the space back. Let's say I have 10GB free, so Xcode says "Well, you just don't have low enough disk

Except Xcode can't possibly know before hand when I do need the space back. Let's say I have 10GB free, so Xcode says "Well, you just don't have low enough disk space to need it deleted" while I'm trying to install Premiere Pro that requires 30GB of space (just an example), but I can't, because I don't have enough disk space. How about not trying to guess when the user needs the space?

MereInterest 4y ago
This is the same problem I have with the "unused RAM is wasted RAM" argument. So long as a system has a maximum of one application using this strategy, it works. As soon as you have two independent programs each of which try to cache as much as possible, it falls apart. For a while, the browser could reasonably assume that it was the only application that used this strategy, and it was a true assumption. Now that native executables are being replaced by web-based applications, every program is trying to maximize its RAM usage, with predictable results.
- astrange 4y ago
  It works fine if they tell the VM that its cache regions are purgeable, so they just go away under pressure instead of getting swapped out. Of course getting swapped out is usually fine too. Huge memory usage is more likely because they don’t know how to check for memory leaks, not because they’re trying to use it.
astrange 4y ago
How’s the “I can’t” work? If the installer is telling you it can’t that just means it’s checking for free disk space the wrong way.
- solarmist 4y ago
  The fact there’s a right way and wrong way to check free disk space is a problem in the first place.
  - astrange 4y ago
    Pretty classic problem. https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use Similar assumptions about filesystems fail if they do data compression or dedupe files - you can easily overestimate how much space something is taking.
    - solarmist 4y ago
      Ah. Ok that makes more sense.

MereInterest 4y ago

This is the same problem I have with the "unused RAM is wasted RAM" argument. So long as a system has a maximum of one application using this strategy, it works. As soon as you have two independent programs each of which try to cache as much as possible, it falls apart. For a while, the browser could reasonably assume that it was the only application that used this strategy, and it was a true assumption. Now that native executables are being replaced by web-based applications, every program is trying to maximize its RAM usage, with predictable results.

astrange 4y ago
It works fine if they tell the VM that its cache regions are purgeable, so they just go away under pressure instead of getting swapped out. Of course getting swapped out is usually fine too. Huge memory usage is more likely because they don’t know how to check for memory leaks, not because they’re trying to use it.

astrange 4y ago

How’s the “I can’t” work? If the installer is telling you it can’t that just means it’s checking for free disk space the wrong way.

solarmist 4y ago
The fact there’s a right way and wrong way to check free disk space is a problem in the first place.
- astrange 4y ago
  Pretty classic problem. https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use Similar assumptions about filesystems fail if they do data compression or dedupe files - you can easily overestimate how much space something is taking.
  - solarmist 4y ago
    Ah. Ok that makes more sense.