I'm currently running motion with 2 cameras on an AMD-K6 500mhz. It's
OK most of the time but due to the box doing other stuff it often hits
100% CPU when motion is being detected.
I've also got a couple of other cameras that I want to put up (all Axis
210 network cams btw).
Anyway, I've been toying with getting a new wiz-bang box but then
stumbled upon openMosix as a way of clustering several less powerful
In a nutshell the machines in the cluster will swap processes between
themselves to share the load and get the most out of the system as a
whole. (This is not like a Beowulf cluster where the software has to be
specially written to run on it).
My motion currently has 7 threads. I know that each net cam will have 2
(if I remember correctly). One processing the incoming stream to
something motion can process and the other doing the motion detection.
So my question (finally!) is this. Do the threads share memory space or
are they separately contained? If they don't share the same memory
space then openMosix should be able to move them around. However if
there is some sharing going on then I might have problems.
While I know a little c I am certainly not proficient enough to gather
this information from the code - Sorry!
The openMosix website can be found at http://openmosix.sourceforge.net/
is anyone is interested.
The lists thoughts are eagerly awaited..
From: William M. Brack <wbrack@mm...> - 2005-11-18 15:55:27
> So my question (finally!) is this. Do the threads share memory space or
> are they separately contained? If they don't share the same memory
> space then openMosix should be able to move them around. However if
> there is some sharing going on then I might have problems.
Motion threads are implemented with the pthread library, and all of the
process's memory space is common between all of the different threads. This
is *very* different from having separate processes, each of which is
Get latest updates about Open Source Projects, Conferences and News.