2018-11-07 14:56:46 -0600 | marked best answer | PNG encoding performance difference between 3.1 and 3.2 Encoding a PNG using OpenCV 3.2.0 takes about 2x longer than OpenCV 3.1.0 on an ARM Cortex A9 system, and about 1.4x longer on an x64 system. Does anyone know what causes the difference and whether it can be reduced through build settings? I'll try git bisect between 3.1 and 3.2 to see what caused the difference but wanted to check if anyone already knows. Thanks Test code (cv.cpp): This is the CMakeLists.txt: To generate cross-compile for ARM I used following cmake command: For intel x64 system (Ubuntu 14.04) I just used: Sample runs on ARM: (more) |
2018-11-07 14:56:46 -0600 | received badge | ● Scholar (source) |
2018-11-07 10:18:12 -0600 | received badge | ● Student (source) |
2018-11-07 10:12:05 -0600 | received badge | ● Self-Learner (source) |
2018-11-06 19:16:03 -0600 | edited answer | PNG encoding performance difference between 3.1 and 3.2 I traced down the commit which changed encode timings to https://github.com/opencv/opencv/commit/1b22783d4636a74512171d6 |
2018-11-06 19:14:00 -0600 | commented question | PNG encoding performance difference between 3.1 and 3.2 I found the commit which changed the timing for me: https://github.com/opencv/opencv/commit/1b22783d4636a74512171d67b95e |
2018-11-06 19:13:52 -0600 | commented question | PNG encoding performance difference between 3.1 and 3.2 I found the commit which changed the timing for me: https://github.com/opencv/opencv/commit/1b22783d4636a74512171d67b95e |
2018-11-06 18:56:42 -0600 | edited answer | PNG encoding performance difference between 3.1 and 3.2 I traced down the commit which changed encode timings to https://github.com/opencv/opencv/commit/1b22783d4636a74512171d6 |
2018-11-06 18:55:32 -0600 | commented question | PNG encoding performance difference between 3.1 and 3.2 I found the commit which changed the timing for me: https://github.com/opencv/opencv/commit/1b22783d4636a74512171d67b95e |
2018-11-06 18:36:06 -0600 | answered a question | PNG encoding performance difference between 3.1 and 3.2 The encode times from the link hash (733fec0) look the same as version 3.2.0 (slower than 3.1). Here is what I see on m |
2018-11-06 18:35:53 -0600 | commented question | PNG encoding performance difference between 3.1 and 3.2 I found the commit which changed the timing: https://github.com/opencv/opencv/commit/1b22783d4636a74512171d67b95e6482f73 |
2018-11-02 18:37:38 -0600 | edited question | PNG encoding performance difference between 3.1 and 3.2 PNG encoding performance difference between 3.1 and master Encoding a PNG using OpenCV 3.2.0 takes about 2x longer than |
2018-11-02 18:37:24 -0600 | received badge | ● Editor (source) |
2018-11-02 18:37:24 -0600 | edited question | PNG encoding performance difference between 3.1 and 3.2 PNG encoding performance difference between 3.1 and 3.2 Encoding a PNG using OpenCV 3.2.0 takes about 2x longer than Ope |
2018-10-31 19:27:34 -0600 | commented question | PNG encoding performance difference between 3.1 and 3.2 The encode times using libraries built from the link hash (733fec0) look the same as version 3.2.0 (slower than 3.1). H |
2018-10-31 18:14:37 -0600 | asked a question | PNG encoding performance difference between 3.1 and 3.2 PNG encoding performance difference between 3.1 and 3.2 Encoding a PNG using OpenCV 3.2.0 takes about 2x longer than Ope |