H.264 Motion Vector Extractor/Performance/x86: Difference between revisions
mNo edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
This section contains the performance metrics for the library running on the x86 platform. | This section contains the performance metrics for the library running on the x86 platform. | ||
= Intel Core i7-8750H @ 2.20 Ghz, 16 GB RAM = | == Intel Core i7-8750H @ 2.20 Ghz, 16 GB RAM == | ||
<br> | <br> | ||
<center> | <center> | ||
| Line 18: | Line 19: | ||
<tr> | <tr> | ||
<td>1920x1080</td> | <td>1920x1080</td> | ||
<td> | <td></td> | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 25: | Line 26: | ||
<tr> | <tr> | ||
<td>3840x2160</td> | <td>3840x2160</td> | ||
<td> | <td></td> | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 33: | Line 34: | ||
</center> | </center> | ||
<br> | <br> | ||
== H.264 Motion Vector Extractor vs FFmpeg == | |||
The following tests were performed with an unusual 3840x2560 resolution and are only intended to show a relative comparison between RidgeRun's solution and FFmpeg for the purpose of extracting motion vectors. For performance metrics please refer to the previous table. | |||
[[File:Libmotion comparison x86 latency.png|600px|thumb|center|Graph of latency per frame for both the FFmpeg and RidgeRun's implementation of a motion vector extractor.]] | |||
[[File:Libmotion comparison x86 cpu.png|600px|thumb|center|Graph of CPU usage for both the FFmpeg and RidgeRun's implementation of a motion vector extractor, along with a baseline GStreamer application.]] | |||
[[File:Libmotion comparison x86 ram.png|600px|thumb|center|Graph of memory usage for both the FFmpeg and RidgeRun's implementation of a motion vector extractor, along with a baseline GStreamer application.]] | |||
<noinclude> | <noinclude> | ||
{{H.264 Motion Vector Extractor/Foot|Performance|Performance/i.MX6}} | {{H.264 Motion Vector Extractor/Foot|Performance|Performance/i.MX6}} | ||
</noinclude> | </noinclude> | ||
Latest revision as of 07:40, 30 August 2022
 | H.264 Motion Vector Extractor RidgeRun documentation is currently under development. |
| H.264 Motion Vector Extractor |
|---|
 |
| H.264 Motion Vector Extractor Basics |
| Getting Started |
| User Guide |
| Examples |
| Performance |
| Contact Us |
This section contains the performance metrics for the library running on the x86 platform.
Intel Core i7-8750H @ 2.20 Ghz, 16 GB RAM
| Resolution | CPU % | Memory (MBs) | FPS | Latency (ms) |
|---|---|---|---|---|
| 1920x1080 | ||||
| 3840x2160 |
H.264 Motion Vector Extractor vs FFmpeg
The following tests were performed with an unusual 3840x2560 resolution and are only intended to show a relative comparison between RidgeRun's solution and FFmpeg for the purpose of extracting motion vectors. For performance metrics please refer to the previous table.
