mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Briggs <jbriggs@briggsmedia.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: athlon guidance
Date: 01 Jun 2003 18:57:47 -0400	[thread overview]
Message-ID: <1054508267.1840.18.camel@family> (raw)

I am attempting to build a 16-camera surveillance system with 8
2-channel multiplexed frame-grabber channels each.. Each channel is read
at at about 5 frames per second, the image converted into JPEG and
saved, and an MPEG-1 clip made at the same time (lots of storage, yes). 
I typically use a small IDE drive for my OS, and a 2-drive RAID-0 built
with WD120JB 8-MB cache drives.  I have learned the hard way that
regular IDE RAID controllers of the Promise type loose interrupts and
result in disk corruption, whereas the 3-ware (with its SCSI-like
hardware) are reliable. There is a LOT of processing and storage going
on here, and I have had good luck on my 8-camera systems using a
GigaByte GA7VAXP with AMD2400XP processors, but average about 10% CPU
utilization for each active (detected motion, now capturing and
encoding) channel.  So when all 8 cameras are active, I sustain about
80% or more total CPU loading.  Typically never more than 5 are active
at the same time.  My question is how can I scale up to get 16 camera
channels?  I use Debian Woody 2.4.19 with Reiserfs (good job Hans!).

The fastest Athlon that I can get is a AMD3200 XP with 400 Mhz FSB. On
the other hand, I can use the Tyan 2466 Dual Athlon board, but MP
processors only have a 266 Mhz FSB and the fastest speed is the 2800
MP.  So, given the nature of the CPU and data intensive application,
which is the faster platform:  a slower 2800/266 MHZ FSB dual processor
or a single 3200/400 MHZ FSB processor? 

All suggestions and analysis welcomed.

Joe




             reply	other threads:[~2003-06-01 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-01 22:57 Joe Briggs [this message]
2003-06-02  7:57 ` [OT] " Leonard Milcin, Jr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1054508267.1840.18.camel@family \
    --to=jbriggs@briggsmedia.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®