Chiebot-Mirror/FFmpeg - FFmpeg - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Nuo Mi	846fbc395b	avcodec/vvc: simplify priority logical to improve performance for 4K/8K For 4K/8K video processing, it's possible to have over 1,000 tasks pending on the executor. In such cases, O(n) and O(log(n)) insertion times are too costly. Reducing this to O(1) will significantly decrease the time spent in critical sections clip \| before \| after \| delta ------------------------------------------------------------\|--------\|--------\|------- VVC_HDR_UHDTV2_OpenGOP_7680x4320_50fps_HLG10.bit \| 24 \| 27 \| 12.5% VVC_HDR_UHDTV2_OpenGOP_7680x4320_50fps_HLG10_HighBitrate.bit\| 12 \| 17 \| 41.7% tears_of_steel_4k_8M_8bit_2000.vvc \| 34 \| 102 \| 200.0% VVC_UHDTV1_OpenGOP_3840x2160_60fps_HLG10.bit \| 126 \| 128 \| 1.6% RitualDance_1920x1080_60_10_420_37_RA.266 \| 350 \| 378 \| 8.0% NovosobornayaSquare_1920x1080.bin \| 341 \| 369 \| 8.2% Tango2_3840x2160_60_10_420_27_LD.266 \| 69 \| 70 \| 1.4% RitualDance_1920x1080_60_10_420_32_LD.266 \| 243 \| 259 \| 6.6% Chimera_8bit_1080P_1000_frames.vvc \| 420 \| 392 \| -6.7% BQTerrace_1920x1080_60_10_420_22_RA.vvc \| 148 \| 144 \| -2.7%	4 months ago
Nuo Mi	40a14ef970	avcodec/executor: remove unused ready callback Due to the nature of multithreading, using a "ready check" mechanism may introduce a deadlock. For example: Suppose all tasks have been submitted to the executor, and the last thread checks the entire list and finds no ready tasks. It then goes to sleep, waiting for a new task. However, for some multithreading-related reason, a task becomes ready after the check. Since no other thread is aware of this and no new tasks are being added to the executor, a deadlock occurs. In VVC, this function is unnecessary because we use a scoreboard. All tasks submitted to the executor are ready tasks.	4 months ago
Nuo Mi	8446e27bf3	avcodec: make a local copy of executor We still need several refactors to improve the current VVC decoder's performance, which will frequently break the API/ABI. To mitigate this, we've copied the executor from avutil to avcodec. Once the API/ABI is stable, we will move this class back to avutil	4 months ago
Zhao Zhili	baf3123c1c	avutil/executor: Allowing thread_count be zero Before the patch, disable threads support at configure/build time was the only method to force zero thread in executor. However, it's common practice for libavcodec to run on caller's thread when user specify thread number to one. And for WASM environment, whether threads are supported needs to be detected at runtime. So executor should support zero thread at runtime. A single thread executor can be useful, e.g., to handle network protocol. So we can't take thread_count one as zero thread, which disabled a valid usercase. Other libraries take -threads 0 to mean auto. Executor as a low level utils doesn't do cpu detect. So take thread_count zero as zero thread, literally. Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>	7 months ago
Nuo Mi	25ecc94d58	avutil: add thread executor The executor design pattern was introduced by java <https://docs.oracle.com/en/java/javase/20/docs/api/java.base/java/util/concurrent/Executor.html> it also adapted by python <https://docs.python.org/3/library/concurrent.futures.html> Compared to handcrafted thread pool management, it greatly simplifies the thread code. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>	1 year ago