Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Niklas Haas <ffmpeg@haasn.xyz>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Hardware purchase request: Ryzen 9 CPU
Date: Fri, 4 Apr 2025 23:19:11 +0200
Message-ID: <20250404231911.GC2094294@haasn.xyz> (raw)
In-Reply-To: <DM8P223MB0365BBE42664B4CE519D52F9BAA92@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Fri, 04 Apr 2025 19:22:26 +0000 "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> wrote:
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Niklas
> > Haas
> > Sent: Freitag, 4. April 2025 19:21
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: [FFmpeg-devel] Hardware purchase request: Ryzen 9 CPU
> > 
> > Hi all,
> > 
> > My current workstation (first generation Zen) is getting rather old (8
> > years).
> > On top of being slow and power hungry, it is also not very
> > representative
> > anymore of modern hardware.
> > 
> > Additionally, I would like to try and incorporate AVX-512 instructions
> > for
> > my swscale rewrite, in particular for the pixel conversions.
> > 
> > The recently released Ryzen 9 series of workstation CPUs are looking
> > very
> > attractive right now; In particular the 9950X3D, which appears at the
> > top of
> > the timed compilation benchmarks.
> > 
> > As such, I am humbly requesting the purchase of this CPU, alongside a
> > suitable
> > mainboard and RAM:
> > 
> > https://de.pcpartpicker.com/list/fFshGJ
> > The total price at time of posting would be 1364 EUR.
> > 
> > Thanks,
> > Niklas
> > _______________________________________________
> 
> Hi Niklas,
> 
> looks like good choices to me!
> 
> But wouldn't it be better to go for an all-new machine rather than upgrading an 8-year-old box?

Hi Softworkz,

I have a much more recent GPU, PSU and SSDs. It's only the MB/CPU/RAM that are
8 years old, everything else has already been swapped out.

> 
> Best,
> sw
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-04-04 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 17:20 Niklas Haas
2025-04-04 18:13 ` Michael Niedermayer
2025-04-04 19:22 ` softworkz .
2025-04-04 21:19   ` Niklas Haas [this message]
2025-04-04 20:41 ` Lynne
2025-04-04 21:22   ` Niklas Haas
2025-04-20  0:10     ` Neal Gompa
2025-04-20 11:14       ` Timo Rothenpieler
2025-04-04 21:54 ` Niklas Haas
2025-04-05 23:10   ` Niklas Haas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250404231911.GC2094294@haasn.xyz \
    --to=ffmpeg@haasn.xyz \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git