Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Hardware purchase request: AVX512-capable laptop
Date: Wed, 3 Jan 2024 04:04:00 +0100 (CET)
Message-ID: <NnCGm7x--3-9@lynne.ee> (raw)
In-Reply-To: <a9f81b4e-20d6-4da3-a7fd-8e0db02f65c9@gmail.com>

Jan 3, 2024, 02:22 by jamrial@gmail.com:

> On 1/2/2024 9:56 PM, Lynne wrote:
>
>> As some of you know, my laptop died nearly 2 years ago, and
>> I've been working on a desktop machine, which is currently a Zen 3.
>> AVX512 has become more popular in the meantime, with Zen 4
>> and future AMD CPUs shipping with it, but currently, we have very
>> little AVX512.
>> In short, I'd like a machine which runs an AVX512-capable
>> AMD CPU, and as the world is opening up more and more, I'd
>> like for it to be portable.
>>
>> I've looked around a lot, but as Intel still has a firm monopoly,
>> the options are limited (7940H(S), 7945HX, 7845HX, 8945HS).
>> What I think I've settled for is an ASUS Vivobook Pro 15, with a
>> 7940HS CPU (the second least powerful Zen 4 mobile CPU),
>>
>
> 7940HS is the highest Ryzen 9 model from the 7040 series. Not sure where you got second least powerful from.
>
> https://en.wikipedia.org/wiki/List_of_AMD_Ryzen_processors#Phoenix_(7040_series,_Zen_4/RDNA3_based)
>

Was reading Wikipedia, and thought it was a Zen 3, my mistake
(and AMD's mistake for making 4 versioning formats):
https://en.wikipedia.org/wiki/List_of_AMD_Ryzen_processors


>> currently trading for 1999.0 EUR on amazon.de.
>>
>> https://www.amazon.de/-/en/Vivobook-Display-R9-7940HS-Windows-Keyboard/dp/B0BRYTS8MR
>>
>> The other alternative I've found is a Lenovo Legion 7 Pro, but
>> it's more expensive at 2399 EUR (currently seems temporarily
>> discounted due to the holidays).
>>
>
> I see a Lenovo Yoga Pro 7 available for 1099 EUR. https://www.amazon.de/-/en/Lenovo-Display-Graphics-Blue-Green-Premium/dp/B0CGLPVQHK/
>
> Same amount of RAM, screen resolution and storage, and a Ryzen 7.
>

It's a good suggestion, but I have a better one, that's somewhat more expensive,
but has a better screen, better build quality, and is cheaper than the Vivobook:

A Lenovo ThinkPad P14s Gen 4 with the following options:
 - Windows 14 Home (if you don't pick Windows, the OLED display is not available for no reason)
 - 32Gb of RAM
 - 1Tb "performance" SSD (it's 70 EUR more, but twice the size)
 - 2880x1800 OLED monitor
 - 4-cell battery (only 10 EUR more)
 - English (EU) keyboard, without backlighting

https://www.lenovo.com/de/de/configurator/cto/index.html?bundleId=21K9CTO1WWDE2

For 1.700,11 EUR. It's made of metal, unlike the Yoga, it's possible to repair,
targeted at business users, has way more ports (including a full-sized RJ-45!),
bigger battery, 3-year warranty instead of a 3-month limited warranty,
and a better keyboard.

We have the budget, as we were looking for ways to spend it anyway,
and it's definitely going to last, so I don't think it's out of an acceptable price range.


>> The Lenovo IdeaPad still hasn't been refreshed and uses a Zen 3 CPU,
>> so it doesn't fit the requirements. I'd take other options, but after
>> all the looking I did, the only other laptops to feature Zen 4 CPUs are
>> rather pricy gaming laptops with high-end NVIDIA GPUs, starting at 2500 EUR
>> and going up.
>>
>
> The Vivobook has a discrete Nvidia GTX 4060, which makes it a gaming focused laptop too.
>

Actually, the Yoga Pro 7 also comes with an NVIDIA GPU, a 4050:
https://www.lenovo.com/de/de/p/laptops/yoga/yoga-pro-series/Yoga-Pro-7-Gen-8-(14-inch-AMD)/LEN101Y0032
(also mentioned it has an NVIDIA GPU on the amazon link, but they seem to be
ashamed of the fact it's a 4050 so they don't mention a model).
The ThinkPad P14s does not have an NVIDIA GPU, which is much less of a plus than
before, but it does save from having a near-constant constant power hog and Optimus display setup.
_______________________________________________
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:[~2024-01-03  3:04 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  0:56 Lynne
2024-01-03  1:22 ` James Almer
2024-01-03  3:04   ` Lynne [this message]
2024-01-03 13:46     ` Michael Niedermayer
2024-01-05 17:36     ` James Almer
     [not found]   ` <NnCGm7x--3-9@lynne.ee-NnCGqE2----9>
2024-01-03  3:30     ` Lynne
2024-01-03  5:28       ` Kieran Kunhya
     [not found]     ` <NnCMnsG--3-9@lynne.ee-NnCMrYP--J-9>
2024-01-09 18:57       ` Lynne
     [not found]       ` <Nnj2jS_--3-9@lynne.ee-Nnj_bOo--3-9>
2024-01-14 17:23         ` Lynne
2024-01-15  8:57           ` Kieran Kunhya
2024-01-15 14:06             ` Paul B Mahol
2024-01-15 16:01               ` Rémi Denis-Courmont
2024-01-15 16:07                 ` Paul B Mahol
2024-01-15 16:10                   ` Nicolas George
2024-01-15 17:30                     ` Michael Niedermayer
2024-01-15 14:59             ` Lynne
2024-01-15 16:01               ` Rémi Denis-Courmont
2024-01-15 17:36                 ` Lynne
2024-01-15 18:50                   ` Kieran Kunhya
2024-01-15 21:47                     ` Michael Niedermayer
2024-01-16  0:03                     ` Lynne
2024-01-16 10:05                       ` Kieran Kunhya
2024-01-16 11:50                         ` Paul B Mahol
2024-01-16 11:54                           ` Kieran Kunhya
2024-01-16 14:59                         ` Lynne
2024-01-17 13:37                           ` Michael Niedermayer
2024-01-17 15:39                             ` Lynne
2024-01-18  3:28                               ` Michael Niedermayer
2024-01-18  4:07                                 ` Lynne
2024-01-18  8:42                                   ` Steve Williams via ffmpeg-devel
2024-01-18  9:52                                   ` Kieran Kunhya
2024-01-18  9:54                                     ` Paul B Mahol
2024-01-18  9:57                                       ` Kieran Kunhya
2024-01-18 17:19                                         ` Paul B Mahol
2024-01-18 22:59                                         ` Michael Niedermayer
     [not found]                                   ` <25e0763a-4b07-4328-ba93-354d23c8e591@advance-software.com-NoQj7Fn----9>
2024-01-18 15:37                                     ` Lynne
     [not found]                                 ` <NoPk9Ny--3-9@lynne.ee-NoPkD07----9>
2024-01-18 12:32                                   ` Lynne
2024-01-05 17:24 ` Rémi Denis-Courmont
2024-01-05 17:31   ` Kieran Kunhya
2024-01-06 10:38   ` Lynne
2024-01-06 11:09     ` Rémi Denis-Courmont
2024-01-06 16:13       ` Lynne
2024-01-06 17:57         ` Rémi Denis-Courmont
2024-01-06 18:01           ` Lynne
     [not found]       ` <NnUYG5V--3-9@lynne.ee-NnUYKEn----9>
2024-01-06 16:21         ` Lynne
2024-01-06 18:11           ` Rémi Denis-Courmont
2024-01-06 18:26             ` Michael Niedermayer
2024-01-06 20:15               ` Rémi Denis-Courmont
2024-01-06 21:06                 ` Lynne
2024-01-06 23:36                   ` Kieran Kunhya
2024-01-07  0:00                     ` Lynne
2024-01-07  0:40                       ` Kieran Kunhya
2024-01-07  1:55                         ` Lynne
2024-01-07  3:14                           ` Kieran Kunhya
2024-01-06 17:59       ` Michael Niedermayer
2024-01-06 18:21         ` Rémi Denis-Courmont
2024-01-06 18:28           ` Lynne
2024-01-06 17:42 ` Michael Niedermayer
2024-01-10  2:31   ` Michael Niedermayer
2024-01-10  2:56     ` Lynne
2024-01-10 13:06       ` Paul B Mahol
2024-01-10 17:58       ` Michael Niedermayer

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=NnCGm7x--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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