On Fri, 19 Apr 2013 14:25:00 +0100, Mike Perkins <
sp...@spam.com>
wrote:
>> Can you name any
>> OS or program that grew smaller over time?
>
>Nope - but that in part due to the increased capability of the software.
How much of the added capabilities do you actually use? When I
upgrade to a newer version, it's rarely to obtain some much needed
feature, but rather in an apparently futile hope that the latest
version will have fewer bugs and crash less often. After about 30
years of personal computing, one would think that I should have
learned the bigger isn't better, but that hasn't happened.
Occasionally, some vendor accidentally produces a relatively bug free
release, that is also fairly useful. XP would be a good example.
That's really bad because if there are no bugs, users would just stay
with the current release forever, not be inspired to upgrade. So, the
next release is full of bugs (and features), so that the upgrade cycle
can be restarted. Sometimes, I suspect that they even introduce bugs
intentionally in order to sell upgrades. Of course, if you complain
about bugs, the standard answer is to wait for the next release which
"should have that fixed". Right.
I am tech support, and I know it all.
I anxiously wait for your latest call.
You've only to play, the game of voice mail,
I'll be there shortly, I'm working my tail.
Now tell me your problem, and what did you do?
This cannot have happened. I haven't a clue.
I may have the answer, though it's slightly late,
Just buy the next version, release, or update.
Next, tell me your problem, no matter how small,
I am tech support, and I know it all...
>I'm more concerned that I can't see conventional computing power getting
>much faster!
I have customers that bought i7 based machines on the assumption that
it would be faster only to discover that only a limited number of
applications can take advantage of 4 cores and a total of 8
(hyperthreaded) processors. I can bring up the task manager, with the
pretty graphs, and demonstrate that most of the cores are doing
nothing. For more mundane applications, there's very little that
multiple cores can do for something like a word processor. For games,
graphics, big arrays, video editing, and CAD, I can see the benefits,
but not for a simple word processor. It's much like a high powered
automobile, capable of doing 200 mph, but stuck in traffic at 10 mph
waiting for other drivers (jobs) to finish so it can lurch forward
quickly and then wait again. Capability does not equal performance.
Much of the CPU time is also spent waiting for I/O. The hard disk is
the current bottleneck. One answer, which is going to be very common
are hybrid drives. That's a multi-gigabloat drive with a
multi-gigabloat flash cache. Kinda like an SSD glued to rotating
memory. For computing that tends to stay in a cache, it's great.
Booting the OS uses the same files every time, so that's a big win.
However, streaming data, that gets read exactly once, can actually be
slower on a hybrid drive than on a conventional drive. However, it's
the latest fashion in computing, and I'll have to endure these until
the prices on SSD drives drops sufficiently to kill them off.
Your quest for more computing power is somewhat futile. Again, if
you're stuck in traffic, a bigger engine is not going to get you there
any faster. Often, you're going at the speed of the slowest vehicle,
or in computing, at the speed of the slowest bus or peripheral. This
month, it's the hard disk that's the bottleneck. For gaming, it's the
video processor. For virtualization and big array crunching, it's the
RAM that slows things down. Put a jet engine in a Volkswagen, and you
still have a Volkswagen.
>> Try running XP SP3 in a virtual machine on a computer with lots of
>> RAM. The OS ends up residing mostly in RAM, rather than bashing the
>> hard disk. It's quite a performance boost (after the initial load).
>
>I think the old PC has 2GB of RAM.
You'll need more to run a VM. The ability to address more than
3.5GBytes of RAM is where 64 bit operating systems shine. Windoze XP
is 32 bits, so you're RAM limited. There was a 64 bit version of XP,
but it seems to have problems. Windoze 7, 8, and Linux on 64 bit
CPU's with 8GB or more RAM works well for XP in a VM.
>One thing that puts me off using a PC 24/7 is the power consumption and
>the associated cost. Have you looked into this? And compared with an
>ARM SBC running Linux?
I have not investigated the power consumption issue. I simply use
what is available and cheap. I'm sure that a lower power SBC and SSD
would draw less power. If I were manufacturing weather stations, it
would be a very different story. I'm currently looking into running a
weather station on a $100 Android tablet, which would certainly be an
improvement in power consumption. It can be done, but it's not
reliable. The LiIon battery does not like to sit forever at 100%
charge and rapidly decays. Android is also not designed for maximum
uptime and tends to reboot, hang, or kill processes over time. Even a
daily midnight reboot doesn't seem to help. However, I'm still hoping
that single application tablet based "servers" will eventually become
a useful idea.
>I thought they had algorithms to rotate any memory changes throughout
>the disk?
Most SSD's have such an algorithm and more. What it does is detect
errors, and reassign alternate blocks in its place. When access time
to any block on the drive is the same, such a system makes good sense.
Some operating systems also have mechanisms to equalize the wear (wear
leveling) on the cells over the entire drive. I killed off several CF
(compact flash) camera cards, that lacked this feature, so I know it's
a real problem:
<
http://en.wikipedia.org/wiki/Flash_file_system>
Still, I worry. When I see the bad sector count climb, I simply
assume that it will continue and eventually kill the drive. This
hasn't happened, but with my customers slipshod (image) backup
frequency, it's a real concern. After a few years of no failures, I
may stop worrying.
>They have now been out a while and still haven't heard any
>horror stories.
Google for "SSD horror stories". The first few hits are worth
reading.
>I'm in the habit of maintaining a couple of backups to
>minimise any disruption.
I do image backups which backs up literally everything. It's faster
and better than any other method I've tried. However, the image
backup software seems universally crude and strange. The least
disgusting of the lot seems to be Acronis True Image, which is my
current favorite. Run it from a boot CDROM, not while the operating
is running, and it will work better and much faster. (Typically 1 - 2
GB/min to USB 2 or 4 GB/min to USB 3).
>I am impressed, my only concern would be overall power consumption and
>its cost.
The computers in the photo were salvaged at the recyclers and cost me
about $30/ea. Pentium III, 3.5" HD, about 2GB RAM, running Windoze
2000. Nothing really special except that they're totally reliable.
Well, I have been killing off cooling fans, but that doesn't really
count. About 55 watts average consumption measure on a kill-a-watt
meter. At $0.20/kw-hr, that's 481 kw-hrs/year or $96/year. Not
great, but also not worth spending several years electricity budget to
reduce the cost. Replacing the 3.5" HD with a flash drive will save
about 10 watts, which I think will be the biggest improvement.
>A hard disk takes more power than a system built around a
>micro. Some of the NXP ARM processors are very affordable and can run
>Linux.
True. The software we're using:
<
http://www.weather-display.com>
also runs on Linux. However, we have other services running on these
machines, such as a ham radio packet email gateway. Much as I would
like to run Linux, the packet stuff is Windoze only at this time.