Axel does not have a secret patch
And now I have such a machine myself. My employer lend me his unneeded T40p and I swapped the harddrive with my installation. I'm sure that I run Haiku without Axel's secret patch and the performance is just as convincing as on his machine. So I must admit that Axel didn't, after all, forget to commit something.
Usually when I run Haiku, I think that we have got one long road ahead with our app_server. But running Haiku on this machine, which has much weaker specs by the way than my other computer, I'm tempted to think there is nothing left to do but fix bugs. The difference is like night and day! Not only is the window redraw absolutely instant without any lag, it is not even using a lot of CPU either. What is the secret of this little machine? Is Haiku bombarded with unkown interrupts, possibly power management related, on newer hardware? Is the IBM using shared memory for the frame buffer (I would think not)? Is our scheduler in love with the first generation Pentium-M and it's chipset? I have no idea, but I'm very curious to find out what it is, because if my other computers are not an exception, it could be very useful information with regards to "unlocking" Haiku on newer and much more powerful machines. I'm interested to know how Haiku performs on other peoples real hardware. Is there a strongly noticable lag when redrawing windows that are exposed by moving other windows, like I see with all my other computers?
- Haiku monthly activity report - September 2019
- Node.js now available in Haiku
- Haiku monthly activity report - 08/2019
- GSOC 2019 Final Report
- Haiku Activity Report: Performance Edition
- new PVS studio scan
- Coding week 4,5,6
- [GSoc 2019] Weeks #4, #5 and #6 progress report
- Haiku monthly activity report - 06/2019
- Coding week no 2 and 3