WeSearch
AVX-512 Optimization for FFmpeg Shows Wild Improvement on AMD Ryzen (2025)

AVX-512 Optimization for FFmpeg Shows Wild Improvement on AMD Ryzen (2025)

·1 min read · 0 reactions · 0 comments · 42 views
More from Phoronix programming Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

The latest AVX-512 optimization for FFmpeg has significantly improved performance on AMD Ryzen processors. The new code path achieves 18 times the speed of standard C code, surpassing the previous AVX2 optimization. This enhancement is particularly beneficial for users with AMD Zen 4 and Zen 5 CPUs.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Phoronix
Read full at Phoronix →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherPhoronix
Canonical URLhttps://www.phoronix.com/news/FFmpeg-AVX-512-uyvytoyuv422
Publication timeThu, 21 May 2026 13:11:54 +0000
Retrieval time2026-05-21T13:21:11.070Z
Last seen2026-05-21T13:21:11.070Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster9AA1BRFy80T-
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Latest AVX-512 Optimization For FFmpeg Shows Wild Improvement On AMD Ryzen Written by Michael Larabel in Multimedia on 18 February 2025 at 08:28 PM EST. 60 Comments Merged today for the widely-used FFmpeg open-source multimedia library was yet another AVX-512 optimized code path... Compared to the pure C code, the AVX2 code path was 10.98x faster while this new AVX-512 code path clocks in at 18x the performance of the common C code. The latest FFmpeg code seeing the AVX-512 treatment is the uyvytoyuv422 function for UYVY to YUV422 format conversion. The AVX-512 optimized code path via hand-written Assembly is a great benefit here. AVX-512 namely found with Intel Xeon processors or all AMD Ryzen and EPYC processors since Zen 4.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Phoronix.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Phoronix