Linked by Thom Holwerda on Wed 29th Sep 2010 22:14 UTC, submitted by Amix
Morphos Bright days ahead for the Amiga world. AROS is doing well, AmigaOS4 is getting one heck of a machine in the AmigaOne X1000, and MorphOS continues its development at a brisk pace. Version 2.6 of MorphOS, currently in development, will add support for (G4, I'm assuming) PowerMacs, which, alongside support for the Mac Mini and eMac, gives MorphOS a solid base of used hardware to run on.
Thread beginning with comment 443262
To view parent comment, click here.
To read all comments associated with this story, please click here.
Neolander
Member since:
2010-03-08

I've never understood the obsession with boot times. Granted, excessive boot times are a pain, but I only boot my computer once in a while. Usually, my system goes into standby when I'm away, and it comes out really quickly.

Short boot times are interesting because cold boot is better than standby for a few reasons :
-No power wasted, except that of the power light. Contrast with keeping RAM (especially) and some other circuitry running for nothing. This issue is voided by hibernation, though, but then boot times become important again.
-Software performance degrades with uptime. There's always a memory leak somewhere, some applications leave processes in the background wasting CPU time for unknown purposes even after they're closed, some crashes have long-term consequences... Fetching a fresh OS image from the disk allows one to go back in a clean state where software runs at full speed and maximum reliability.

Reply Parent Score: 3

Drumhellar Member since:
2005-07-12

This issue is voided by hibernation, though, but then boot times become important again.


With hibernation, boot times is scarcely more than loading a ram image off the hard disk. That's fine for 2GB of ram. I wonder how practical it is for 16GB?

oftware performance degrades with uptime. There's always a memory leak somewhere, some applications leave processes in the background wasting CPU time for unknown purposes even after they're closed, some crashes have long-term consequences... Fetching a fresh OS image from the disk allows one to go back in a clean state where software runs at full speed and maximum reliability.


I have to disagree with this statment. This isn't the days of Windows 98. My system doesn't degrade as uptime increases, and Windows does a fine damn job of shutting down processes. Also, the software I use is well written, and doesn't normally doesn't leak memory. If it does, I restart only the app in question, and sanity is returned.

Reply Parent Score: 2

Neolander Member since:
2010-03-08

With hibernation, boot times is scarcely more than loading a ram image off the hard disk. That's fine for 2GB of ram. I wonder how practical it is for 16GB?

That was my point, although I expressed it awfully. Going back from hibernation to a working state with several GBs of RAM is already taking times close to that of cold boot, making use of hibernation questionable. With even more RAM, cold boot would become a better option.

An interesting point to make is that if RAM amount grows, power consumption during standby is going to grow too, since RAM manufacturers don't exactly care about it.

On the other hand, I hope that we'll soon stop making more and more powerful machines just for running a desktop OS and word and start instead to work on making Windows and Word eat less resource so that they can work on less powerful, and hence less power-hungry machines.

The common usage patterns of a desktop computer could easily be applied to a 1 GHz P4 with 512MB RAM if software was optimized a little bit. With more aggressive optimization, a 300 MHz PII with 128MB RAM could probably work (although I'm not sure of that one, because of new trends like hi-res displays and heavily-compressed data that require some power). GPU acceleration should not be ever needed outside of the gaming and HD video area.

I have to disagree with this statment. This isn't the days of Windows 98. My system doesn't degrade as uptime increases, and Windows does a fine damn job of shutting down processes. Also, the software I use is well written, and doesn't normally doesn't leak memory. If it does, I restart only the app in question, and sanity is returned.

On computers with insanely powerful processors and large amounts of RAM like my new laptop, you don't notice this phenomenon much if you regularly turn your computer off, but on my old computer (Athlon 2400+, 512MB RAM), you could clearly see the computer slowing down and begin to swap as time passed. I'm not talking about keeping apps open : even when closing apps and opening them back, there was still some RAM missing, so it was the OS and background processes&services which were trashing it.

This computer was not running win9x, it was running XP, so more or less the same Windows NT kernel that we have now. If you know where the amount of actually used (not cached) RAM can be read on Windows 7, I can tell you if there have been improvements on the area or if memory is still slowly trashed.

My conclusion from this is that if we're going to finally go back to low-performance computers in order to reduce our power consumption and face all performance issues of modern software instead of just running it on faster hardware, we'd better take these problems into consideration.

Edited 2010-09-30 16:31 UTC

Reply Parent Score: 4

n.l.o Member since:
2009-09-14

I have to disagree with this statment. This isn't the days of Windows 98. My system doesn't degrade as uptime increases, and Windows does a fine damn job of shutting down processes. Also, the software I use is well written, and doesn't normally doesn't leak memory. If it does, I restart only the app in question, and sanity is returned.


MorphOS has no memory protection, memory leaks can cause havoc.

A two or three second boot time is essential.

Reply Parent Score: 1