5 ms·
Some anecdotal experience: - we switched our nodejs workload to graviton (c6g from c5), and it resulted in needing more instances, which ended up costing nearl
by forty 5y ago
Some anecdotal experience:
- we switched our nodejs workload to graviton (c6g from c5), and it resulted in needing more instances, which ended up costing nearly exactly the same price
- ARM is annoying in practice for some stuff (we build our docker images on our CI which is on premise and not ARM)
- AWS pushed a bit to have us move to graviton
- Where are the c6a ? :)
- philliphaydon 5y agoI moved a .net core project to t4g from t3 and it resulted in lower cpu utilisation and requests being returned quicker.
- zapdrive 5y agoNice try, Intel.
- forty 5y agoHaha at home I'm an AMD fanboy - personal laptop is a Ryzen 4750u - and I happen to collect ARM single board computers, so I think I'm pretty open minded when it comes to CPU choice (and btw in those c6a instances I'd love to try, the "a" means AMD ^^)
- eric-hu 5y agoCan you describe more about the nature of your workloads?
- forty 5y agoThose are HTTP APIs which are mostly reading from MySQL and S3. They are running on nodejs 12 (soon 16 ^^). They are using quite a lot of CPU, probably mostly due to having to parse large amount of JSON, and a bunch of cryptographic operations (mostly hmacs, AES - we are only using nodejs built-in crypto primitive) - but I don't know for sure to be honest - hence the choice of C type instances.
- pclmulqdq 5y agoThis workload looks really well suited for x86 cores. The x86 architecture has big advantages in both crypto and fast string parsing. It's interesting that graviton got cost parity given what you said.
- floatboth 5y agoThe only "big advantage" I can think of is that libraries like simdjson usually are still written for AVX first, NEON later. Otherwise it's not so clear cut, especially if not using any libraries like that.
- freemint 5y agoAnd SVE even later.
- floatboth 5y agoSVE hardware has been made of unobtainium so far. Graviton3 will change that pretty soon though.
- pclmulqdq 5y agoAlso, the datapath is a lot wider: NEON only does 16 bytes per vector, while Intel has fixed most of its frequency issues and can go up to 32 bytes per vector without throttling. AVX is also a lot more expressive, and can do more per instruction.
- forty 5y agoI have no idea if nodejs is taking advantage of this to be honest.
- skavi 5y agoSVE2 seems great though [0]. It looks at least as nice to use as AVX512. Graviton3 has SVE2, though I'm not sure what vector length they use. [0]: https://developer.arm.com/documentation/ddi0602/2021-09/SVE-Instructions https://developer.arm.com/documentation/ddi0602/2021-09/SVE-...