<samueldr>
>> GIGABYTE does not publish pricing of the ThunderXStation, but we have reached out to PhoenicsElectronics and will update the story once we get more information on the matter.
<samueldr>
on a need to know basis
<gchristensen>
more than 3 $'s
<samueldr>
I can smell the order of magnitudes
<samueldr>
though, as stated previously, this is a replacement for the daily routine, I intend to keep the firepower around and networked ready to use
<samueldr>
the starling is a no-go, no 1440p or 4k 2x monitor output
<gchristensen>
sounsd right
<gchristensen>
starling is a server :)
<samueldr>
:)
<grw>
they have another for ~1300 though, uses old thunderx chip though
<grw>
think it is a lot slower
<grw>
it looks like starling is first gen too
<gchristensen>
first gen gets you slow clock but lots of cores
<samueldr>
if I was into the market of getting a local build farm they would be more interesting alternatives
<samueldr>
the 96boards workstation is the first one you linked I hadn't seen
<samueldr>
had seen other boards from them, but not that workstation
<grw>
SOC only uses 5W power
<grw>
so crazy :)
<grw>
must be slow though
<samueldr>
>> Renegade Elite is designed from the ground up as a high performance solution using up to 15W
<samueldr>
are they using fudgy maths?
<grw>
the workstation i mean
<samueldr>
(I have so much to learn on the hardware side)
<samueldr>
yeah, uh, let me rephrase: would the renegade elite really use 15W?
<samueldr>
if that 24-core Cortex-A54 uses a third of the power?
<grw>
i think so, if you really push it
<thefloweringash>
What’s the cooling situation like? A rockpro64, for example, has a mount for a heatsink and fan.
<grw>
rk3399 has GPU, a72 cores and almost double the clock
<samueldr>
thefloweringash: AFAICT the case serves to sink some heat
<samueldr>
otherwise nothing specific in sight
<samueldr>
it seems to sit the CPU on the case
<andi->
gchristensen: I didn't buy the other one we talked a out last year/early this year because the vendor wasn't really helping in regards to openbmc etc.. And I would probably not do it differently when looking at them this time around.
<andi->
Regarding workstation: I would probably get two boxes... One aarch64 box for compute and one box where GPU doesn't mean outdated, insecure & bloby kernels
shad has quit [Remote host closed the connection]
shad has joined #nixos-aarch64
shad has quit [Remote host closed the connection]
shad has joined #nixos-aarch64
orivej has joined #nixos-aarch64
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-aarch64
Acou_Bass has quit [Quit: byeeeeeeeeeeeeeee]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Read error: Connection reset by peer]