From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Build machines
Date: Mon, 17 Apr 2023 21:05:59 +0200 [thread overview]
Message-ID: <87mt36nxbc.fsf@Rainer.invalid> (raw)
In-Reply-To: <87r0snd0w3.fsf@Rainer.invalid> (Achim Gratz via Cygwin-apps's message of "Thu, 13 Apr 2023 21:42:52 +0200")
Achim Gratz via Cygwin-apps writes:
> The original plan was to make this my new Linux desktop and replace the
> 9 year old Haswell I'm using right now and wait until the 16-core
> Phoenix processors are finally available, but I'll probably have to
> re-think that.
I misremembered the code names. The direct successor to the 7735HS
(Rembrandt Refresh) are the 7840HS / 7940HS (Phoenix-H at 8 cores and
upgraded to 4nm Zen4/RDNA3 and about 15% better performance per Watt);
the upcoming 16 core is the 7945HX (Dragon Range, 5nm Zen4/RDNA2).
Anyway, I just ordered another of one these to become my new Linux
desktop, the first one will stay with Win11 Pro and Cygwin and become my
new build box in the coming weeks. I added a 4TB SSD for archival
storage last weekend, for now I'll keep the 500GB NVMe it came with for
OS and builds as it seems to not limit anything in any meaningful way
for now. If it turns out later that it does I'll just switch to a
speedy 2TB NVMe later on (I already had one, but that will go into #2 as
system / home drive as per the original plan).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2023-04-17 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:42 Achim Gratz
2023-04-17 19:05 ` Achim Gratz [this message]
2023-06-24 11:40 ` ASSI
2024-05-11 14:15 ` ASSI
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=87mt36nxbc.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).