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. Re: Motion 4.2.2 vs 4.1.1 CPU usage (tosiara)
2. Re: Motion 4.2.2 vs 4.1.1 CPU usage (rmbusy)
3. Re: Motion 4.2.2 vs 4.1.1 CPU usage (oleg.chekalin)
----------------------------------------------------------------------
Message: 1
Date: Sat, 20 Jul 2019 18:53:49 +0300
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Motion 4.2.2 vs 4.1.1 CPU usage
Message-ID:
<cachtdwr_yeyf_d_wx7-zjl83cwgai5fn39vjchtjnqkd_uc...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I have tested RTSP H264 1280x960 20 fps running on ARM ODROID C1.
Just running, without any recording it takes 130% CPU. 4.1.1, 4.2.2, Ubuntu
16.04 and 18.04 - the result was always the same. NEON optimizations
reduced to 125%, not much. Pretty all the time motion was decoding H264.
The decoding, as already mentioned, is very CPU intensive
On Sat, Jul 20, 2019 at 5:36 PM Colin Law <[email protected]> wrote:
> On Sat, 20 Jul 2019 at 15:24, John D. Gwinner <[email protected]> wrote:
>
>> Ok, that helps me with my project ? we need to get 15fps or 30fps; (it?s
>> a medical project).
>>
>>
>>
>> If you?re getting 2-5 and that high a CPU rate, clearly we?ll never get
>> to 15.
>>
>
> It also depends dramatically on the format of the data. If it is mpjpeg
> for example then motion need do very little to decode the image, if however
> it is H264 then there is a vast amount of work required just extracting the
> images from the stream. On my system running an H264 camera a lot more
> processor time is spent decoding the stream than is spent in 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
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sat, 20 Jul 2019 09:37:51 -0700
From: rmbusy <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Motion 4.2.2 vs 4.1.1 CPU usage
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On Sat, 20 Jul 2019 at 15:24, John D. Gwinner <[email protected]
<mailto:[email protected]>> wrote:
Ok, that helps me with my project ? we need to get 15fps or 30fps;
(it?s a medical project).
If you?re getting 2-5 and that high a CPU rate, clearly we?ll never
get to 15.
The Rock64 (and new RockPro64) have a built in GPU.? I've been working
on getting a ffmpeg build with the GPU enabled going, for H.264 stream
decoding, but don't have it working yet.? I was hoping that would
significantly reduce the CPU usage for stream decoding, but don't know
yet if it will, or by how much.
In my case, I have 3 streaming cameras, and 5 snapshot cameras, so 8
total.? If you're only using 1 camera, a quad core processor like the
Rock64 should easily be able to handle 15 FPS, or more. BTW, While I was
updating the OS on my Rock, I moved Motion to a Core 2 Duo i7 based
laptop.? My CPU usage there was around 175% to 200% for the same
configuration.
I chose the Rock64 for the quad core, USB3.0, and Gigabit Ethernet
interfaces.? Something RPi didn't have at that time.? I played around
with Motion on a RPi-2, and 2 streaming cameras at 15FPS maxed it out.?
That was a couple years ago, so improvements in the software should help.
--
Rob.
On 7/20/19 8:53 AM, tosiara wrote:
> I have tested RTSP H264 1280x960 20 fps running on ARM ODROID C1.
> Just running, without any recording it takes 130% CPU. 4.1.1, 4.2.2,
> Ubuntu 16.04 and 18.04 - the result was always the same. NEON
> optimizations reduced to 125%, not much. Pretty all the time motion
> was decoding H264. The decoding, as already mentioned, is very CPU
> intensive
>
> On Sat, Jul 20, 2019 at 5:36 PM Colin Law <[email protected]
> <mailto:[email protected]>> wrote:
>
> On Sat, 20 Jul 2019 at 15:24, John D. Gwinner <[email protected]
> <mailto:[email protected]>> wrote:
>
> Ok, that helps me with my project ? we need to get 15fps or
> 30fps; (it?s a medical project).
>
> If you?re getting 2-5 and that high a CPU rate, clearly we?ll
> never get to 15.
>
>
> It also depends dramatically on the format of the data.? If it is
> mpjpeg for example then motion need do very little to decode the
> image, if however it is H264 then there is a vast amount of work
> required just extracting the images from the stream.? On my system
> running an H264 camera a lot more processor time is spent decoding
> the stream than is spent in motion detection.
>
> Colin
> _______________________________________________
> Motion-user mailing list
> [email protected]
> <mailto:[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
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sat, 20 Jul 2019 19:54:01 +0300
From: "oleg.chekalin" <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Motion 4.2.2 vs 4.1.1 CPU usage
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 157, Issue 34
********************************************
