The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Geovision and Atom Motherboards



I've been playing with an Atom Motherboard as the heart of my Windows
Home
Server. Before I finally commission the system I thought I'd try it with my
old Geovision G650V3 card and the Geovision V6.05 software.

I was surprised at how successful it was.

My 5ish year old system was an Intel P4 2.8Ghz on an ASUS P4P800S Mb with
1Gb of RAM stuck on Windows XP SP1 (see previous notes). That runs at about
16% CPU busy with the TCIP and Webserver running. This runs with 5 cameras
at 640x480 with Geovisions own software compression. Four cameras are
recording 24x7, the last one doing motion detect only. One remote user on
the webserver app gives 24 - 28% CPU, strangely two users don't seem to
increase the CPU much.

Total 102w of power.

The new ATOM runs at 40w, using a Laptop drive as boot drive. the case and
PSU are the WHS ones. 2Gb memory with XP SP3. CPU was less, with 8%ish no
users, 12-15 with one. 18-20 with two.

The cameras are set up the same but only recording at 320x240 for some
reason. I remember ages ago that there was an oddity.and you had to do
additional steps to get the full quality. Anyone remember what you had to
do?


So that leaves me in a dilemma. Do I swap in the ATOM for the Geovision
machine and then get a new one for the WHS of get a more powerful CPU and
MB
for the HWS (Quad core) and run it under Hyper V and move more things to
it.

This testing means that the WHS note on the forum will resume next week.


Simon


[Non-text portions of this message have been removed]



------------------------------------


UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.