Announcement

Collapse
No announcement yet.

Haiku Operating System Gets Moving With Clang, Driver Fixes

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Haiku Operating System Gets Moving With Clang, Driver Fixes

    Phoronix: Haiku Operating System Gets Moving With Clang, Driver Fixes

    It's been just over one month since the long awaited release of Haiku R1 Beta 1 for reliving the BeOS experience as open-source. While it was a momentous occasion, the developers have continued advancing this free software platform...

    http://www.phoronix.com/scan.php?pag...d-Driver-Fixes

  • Zan Lynx
    replied
    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.

    Leave a comment:


  • cb88
    replied
    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.
    No what I mean was more like what happens with bufferbloat mitigations where no application gets 100% of the disk usage quota... which maintains latency in user interactions at reasonable levels but means you don't get peak performance in all cases. Modern OSes can be wasteful of IOPS, which is what kills non SSD users. Haiku actual already combats a little of this by havving alot of the file meta data located along side the data on the disk as extents.

    Leave a comment:


  • Zan Lynx
    replied
    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.
    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:


  • cb88
    replied
    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.
    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.

    Leave a comment:


  • stibium
    replied
    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.
    It's also designed to be completely responsive under full load. Try that with Linux at full disk load.

    Leave a comment:


  • cb88
    replied
    Originally posted by RavFX View Post
    My wifi work only for like 5 to 10 minutes, if not less. It use to work fine like 2-3 years ago.
    You should post your /var/log/syslog when this occurs... also note that there have been alot of wifi / ethernet related fixes in the past few days that may get backported into the beta1 via the software update feature.

    Leave a comment:


  • cb88
    replied
    Originally posted by thunderbird32 View Post
    Wish Haiku Beta 1 would work correctly on VirtualBox. It just causes a "guru meditation" error during boot (post-install).
    It works fine in VirtualBox you must be doing something specific that breaks it. Also I would suggest you use the 32bit hybrid version as it has more applications available currently. Maybe by next release the 64bit version will have more.

    Leave a comment:


  • cb88
    replied
    Originally posted by Nuc!eoN View Post
    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
    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.

    Leave a comment:


  • Nuc!eoN
    replied
    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:

Working...
X