Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Questions on CPU load and motion detection level (Willy Gardiol)
2. Re: Questions on CPU load and motion detection level (Colin Law)
3. Re: Questions on CPU load and motion detection level (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Wed, 30 Jan 2019 15:01:25 +0100
From: Willy Gardiol <[email protected]>
To: [email protected]
Subject: [Motion-user] Questions on CPU load and motion detection
level
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
I managed to decrease my CPU load from over 60% to 25% by:
- carefully setting width/height to match cameras
- lowering camera image output when possible from 1280x1024 to 800x600
- enabling HW acceleration for x264 in ffmpeg (on Intel hardware) and
setting ffmpeg_video_codec mp4:h264_vaapi
With motion detection enabled for most of the cameras.
Thank you for this amazing piece of software!
One last question on the RTSP cameras:
they are fixed to 1280x720 resolution, would be a good idea to force a
lower width/height so to speed up motion detection, or the added cpu
load to resize the frame will be more then the gain? I am askinh because
at the moment i don't do motion detection on the RTSP cameras.
On 01/25/2019 05:21 PM, Colin Law wrote:
> And make sure the size in the config file matches exactly that from
> the camera (you can view the camera in VLC, for example, and check
> what the image size is if necessary). If Motion has to resize that
> will use a lot of CPU.
>
> Colin
>
>
> On Fri, 25 Jan 2019 at 13:32, tosiara <[email protected]> wrote:
>> I'd recommend you to connect a single camera and play with params
>> before you get familiar with how motion works. And then add on by one
>> any additional
>> Height and width must be specified in the config
>> It is normal to see such cpu usage if you are using motion detection
>>
>> On Fri, Jan 25, 2019 at 3:23 PM Willy Gardiol via Motion-user
>> <[email protected]> wrote:
>>>
>>> Hi!
>>>
>>> i have installed Motion with success, it's an amazing piece of software
>>> and i love it so far.
>>>
>>> My setup is:
>>>
>>> 5 IP Axis cameras (configured using URL
>>> http://10.0.0.X/axis-cgi/jpg/image.cgi?resolution=1280x1024)
>>>
>>> 4 Chinese V380 IP cameras (configured using URL
>>> rtsp://10.0.0.Y:554/live/ch00_1)
>>>
>>> The server is a small form PC with a Intel(R) Celeron(R) CPU G1840 @
>>> 2.80GHz, 8Gb RAM and some storage space.
>>>
>>> Things works, but i have a few areas where i would like to better
>>> understand what is going on.
>>>
>>> I see that, with motion detection active, some cameras are always
>>> recording (300Gb+ in a couple of days) while others simply never detect
>>> any motion.
>>>
>>> CPU load is quite high, on the 40% level constantly IF i disable motion
>>> detection. With motion detection active, it goes up to 80/90% of CPU.
>>>
>>> I tried adding the option "movie_passthrough on" to the cameras, but
>>> nothing has changed.
>>>
>>> My questions:
>>>
>>> 1. Should i specify a width/height for each camera? The two set of
>>> cameras have different resolutions
>>>
>>> 2. How can i check motion detection, and tune it so that it is more
>>> reasonable?
>>>
>>> 3. How can i lower CPU usage? Change video codecs? Reduce image resolution?
>>>
>>>
>>> thank you, also if you can point me to resources to deepen these topics.
>>>
>>>
>>>
>>> _______________________________________________
>>> Motion-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> https://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 2
Date: Wed, 30 Jan 2019 14:38:47 +0000
From: Colin Law <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Questions on CPU load and motion detection
level
Message-ID:
<CAL=0gluv13duj9adazbqfpsbyysywvt1von0yesu9fqy_za...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Wed, 30 Jan 2019 at 14:01, Willy Gardiol via Motion-user
<[email protected]> wrote:
> ...
> One last question on the RTSP cameras:
>
> they are fixed to 1280x720 resolution, would be a good idea to force a
> lower width/height so to speed up motion detection, or the added cpu
> load to resize the frame will be more then the gain? I am askinh because
> at the moment i don't do motion detection on the RTSP cameras.
I think it is almost impossible to predict that answer to that
question. It is easy enough to try it and see. Have you also slowed
the frame rate down for the detection? Probably something like 4/sec
is enough for motion detection.
Colin
------------------------------
Message: 3
Date: Wed, 30 Jan 2019 16:46:44 +0200
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Questions on CPU load and motion detection
level
Message-ID:
<cachtdwqnvkqqqal2xe6vvdqvldftnn1+fvgykc8upenvz9s...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Motion has built-in limit for motion detection frame rate. It's 3 fps
Resizing a frame prior performing heavy motion detection may be a good
idea, especially using cpu-optimized code, but it should be
configurable. As in this case you would loose precision. Worth to
create a feature request in Github's issue tracker
On Wed, Jan 30, 2019 at 4:40 PM Colin Law <[email protected]> wrote:
>
> On Wed, 30 Jan 2019 at 14:01, Willy Gardiol via Motion-user
> <[email protected]> wrote:
> > ...
> > One last question on the RTSP cameras:
> >
> > they are fixed to 1280x720 resolution, would be a good idea to force a
> > lower width/height so to speed up motion detection, or the added cpu
> > load to resize the frame will be more then the gain? I am askinh because
> > at the moment i don't do motion detection on the RTSP cameras.
>
> I think it is almost impossible to predict that answer to that
> question. It is easy enough to try it and see. Have you also slowed
> the frame rate down for the detection? Probably something like 4/sec
> is enough for motion detection.
>
> Colin
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 151, Issue 49
********************************************
