Linux is doing that about as well as it can be done now I think.
The BFQ MQ scheduler does a good job. Even during a BTRFS array scrub I can use my NAS. I can still feel the annoying little pause, pause, act delay though.
Announcement
Collapse
No announcement yet.
Haiku Operating System Gets Moving With Clang, Driver Fixes
Collapse
X
-
Originally posted by Zan Lynx View Post
Every OS has problems with disk IO. It's unavoidable when you are using memory mapping and on-demand paging for your executables and libraries. Not to mention the data files.
I suppose that you could page-in and memory lock everything for the foreground application, which would isolate it from disk IO. But most apps don't use the majority of their libraries. They don't even use all of their executable because of rarely used exception and error handlers. Loading those in is a waste of RAM.
Data files are even worse. There's no way for the OS to predict the usage.
Disk access latency is the killer. Even if you gave the foreground application immediate access to the next disk queue slot, that's as much as 15 ms to finish the current operation on a slow spinning disk. Then what, are you going to leave the disk completely idle so that unknown future operations have minimum latency? For how long?
I think we just upgrade everyone to NVMe Flash. Even SATA solid-state is good. Latency is in microseconds, not milliseconds.
Leave a comment:
-
Originally posted by cb88 View Post
Actually under full disk load Haiku still has issues, it's more noticeable with slow disks though. The Haiku IO scheduler could probably use some improvements in that area.
I suppose that you could page-in and memory lock everything for the foreground application, which would isolate it from disk IO. But most apps don't use the majority of their libraries. They don't even use all of their executable because of rarely used exception and error handlers. Loading those in is a waste of RAM.
Data files are even worse. There's no way for the OS to predict the usage.
Disk access latency is the killer. Even if you gave the foreground application immediate access to the next disk queue slot, that's as much as 15 ms to finish the current operation on a slow spinning disk. Then what, are you going to leave the disk completely idle so that unknown future operations have minimum latency? For how long?
I think we just upgrade everyone to NVMe Flash. Even SATA solid-state is good. Latency is in microseconds, not milliseconds.
Leave a comment:
-
Originally posted by stibium View Post
It's also designed to be completely responsive under full load. Try that with Linux at full disk load.
- Likes 1
Leave a comment:
-
Originally posted by cb88 View Post
It's a personal desktop workstation OS. Linux/Windows do not have this same focus (Linux mostly focuses on Servers , and Windows used to have this focus but has lost it, even when it did have this focus it was lacking in man areas that BeOS/Haiku excelled at).
It's designed to be responsive, easy to use and customize with sane defaults.
You could port all the UI and everything to Linux, and Barrett, V/OS is doing just this, however you would still loose out on the developer end where C++ is used where it is convenient and sensible in the kernel unlike Linux that has a hard ban on it.
Another aspect is the design of the Be API lends itself to good multithreading design in the applications... build in message passing as standard.
- Likes 1
Leave a comment:
-
Originally posted by RavFX View PostMy wifi work only for like 5 to 10 minutes, if not less. It use to work fine like 2-3 years ago.
Leave a comment:
-
Originally posted by thunderbird32 View PostWish Haiku Beta 1 would work correctly on VirtualBox. It just causes a "guru meditation" error during boot (post-install).
Leave a comment:
-
Originally posted by Nuc!eoN View PostCan anybody tell me what is the fuzz about Haiku? Why are so many people keen to use a BeOS like system? What are the benefits compared to other OSes
It's designed to be responsive, easy to use and customize with sane defaults.
You could port all the UI and everything to Linux, and Barrett, V/OS is doing just this, however you would still loose out on the developer end where C++ is used where it is convenient and sensible in the kernel unlike Linux that has a hard ban on it.
Another aspect is the design of the Be API lends itself to good multithreading design in the applications... build in message passing as standard.
- Likes 1
Leave a comment:
-
Can anybody tell me what is the fuzz about Haiku? Why are so many people keen to use a BeOS like system? What are the benefits compared to other OSes
Leave a comment:
-
The improved network drivers sure are nice. But the latest nightlies fail to boot correctly, they boot to a terminal only. So I can't really test if Wi-FI works fine now
Leave a comment:
Leave a comment: