From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] AVX512 NUCs for FATE and development
Date: Thu, 08 Dec 2022 22:29:28 +0100
Message-ID: <dd4370e4-78bb-4522-b435-cd3fd5f9f04c@betaapp.fastmail.com> (raw)
In-Reply-To: <CAEEMt2k8MN5Evas_31_uXDJgNu9WAWF3LzgpjK0oWUsDJiNNqA@mail.gmail.com>
On Thu, 8 Dec 2022, at 22:20, Ronald S. Bultje wrote:
> Hi,
>
> On Sun, Dec 4, 2022 at 1:08 PM Kieran Kunhya <kierank@obe.tv> wrote:
>
>> Hello,
>>
>> As discussed at the developer meeting it would be good to have an AVX-512
>> (ICL) FATE machine and also a development machine.
>> What I didn't realise until a few weeks ago is that 11th Generation NUCs
>> have AVX512ICL support.
>>
>> I suggest buying:
>>
>> 2x
>>
>> https://www.scan.co.uk/products/intel-nuc-bnuc11tnki70000-rocket-lake-core-i7-1165g7-dual-ddr4-so-dimm-slots-intel-iris-xe-graphics
>> - £529 each
>> 2x 2x 16GB RAM - 32GB in each (price TBC as I want to buy the right one,
>> RAM can be confusing)
>> 2x M.2 NVMe SSDs -
>>
>> https://www.amazon.co.uk/WD_BLACK-Internal-Gaming-Technology-speeds/dp/B08KFN1KT1
>>
>> £1500 total I would estimate.
>>
>> I am happy to host these (as with the M1s) but as these are NUCs anyone can
>> buy and host them easily.
>>
>
> +1 from me - AVX512-icelake is where a lot of x86 SIMD dev takes place in
> the next few years, and testing this new SIMD code in FATE is critical.
+1 from me too.
--
Jean-Baptiste Kempf - President
+33 672 704 734
_______________________________________________
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".
next prev parent reply other threads:[~2022-12-08 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 18:08 Kieran Kunhya
2022-12-08 21:20 ` Ronald S. Bultje
2022-12-08 21:29 ` Jean-Baptiste Kempf [this message]
2022-12-08 21:40 ` Kieran Kunhya
2022-12-09 17:07 ` Michael Niedermayer
2022-12-10 18:10 ` Carl Eugen Hoyos
2022-12-17 19:57 ` Kieran Kunhya
2022-12-17 20:46 ` Michael Niedermayer
2022-12-18 10:41 ` Stefano Sabatini
2023-01-03 11:23 ` Kieran Kunhya
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=dd4370e4-78bb-4522-b435-cd3fd5f9f04c@betaapp.fastmail.com \
--to=jb@videolan.org \
--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