Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by foota on Wednesday May 03, 2023 @05:36PM
(#35808116)
You're probably leaving a lot of performance on the floor if you're building for haskell and running on skylakeish or newer.
Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by nickpeterson on Wednesday May 03, 2023 @05:46PM
(#35808216)
*haswell, in case the Haskell people come after you.
Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by speed_spread on Wednesday May 03, 2023 @06:25PM
(#35808629)
"don't poke the endofunctor"
Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by paulddraper on Wednesday May 03, 2023 @06:06PM
(#35808430)
Ah, that makes more sense.
Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by stingraycharles on Thursday May 04, 2023 @01:05AM
(#35811441)
Yeah we know, it’s just that we ship these binaries to customers and need a reasonably old architecture that we know “almost everyone” uses.
Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by Aeolun on Wednesday May 03, 2023 @10:00PM
(#35810391)
Why not use the c type instances? Is the compilation memory bound? I’d expect it to be the cpu that’s the limiting factor.
Re:Graviton 3, Apple M2 and Qualcomm 8cx 3rd gen: a URL pars...
by stingraycharles on Thursday May 04, 2023 @01:04AM
(#35811431)
Heavy C++ template metaprogramming, we need up to 4GB of memory per process in some situations.
Of course the types of optimisations that a compiler may (or may not) do on aarch64 vs x86_64 are completely different and may explain the difference (we actually compile with -march=haswell for x86_64), but generally Graviton seems like a really good deal.