3 ms·
> Because people complain their system is "slow" if it blocks on disk I/O. Yeah, I/O blocks drive me mad every time. They are more noticeable on Windows though
by qwerty456127 3y ago
> Because people complain their system is "slow" if it blocks on disk I/O.
Yeah, I/O blocks drive me mad every time. They are more noticeable on Windows though. Perhaps that's because Windows doesn't RAM-cache enough and I do a lot of USB I/O (USB NIC, USB drives).
> Another set of people also complain Linux takes too long to safely unplug USB drives.
If only it had an APIs to see how much RAM of a specific device is RAM-cached rigth now and visualize the progress of flushing that cache... Unvisualized long I/O (incl. caching) operations, let alone those freezing the UI, indeed feel bad and are a UX bug.
One of the key reasons I prefer Linux over Windows is Linux is much more rare to freeze, no matter the workload.
- qwerty456127 3y ago> If only it had an APIs to see how much RAM of a specific device is RAM-cached rigth now This is a typo, should have been "If only it had an APIs to see how much of a specific device is RAM-cached right now".
- suprjami 3y agoI've also thought it would be nice if Linux's dirty page handling was more granular. But at the same time, whenever dirty pages are a concern it's usually one large file or one NFS mount or one USB device. The system otherwise doesn't have a great deal of dirty pages to bother reporting on. Also programs have access to selective file flushing with fsync() so there is at least that.