3 ms·
I would start to look into using ROCm/HIP to port the code. Some of it can be done automatically and some will need customizations [0]. Then, you rent time on m
by latchkey 3y ago
I would start to look into using ROCm/HIP to port the code. Some of it can be done automatically and some will need customizations [0]. Then, you rent time on my systems and see what the performance is. If it is good, you rent more, for longer to bring the pricing down. Effectively, we are taking the capex/opex risk off your shoulders. The key point here is that we have actual availability and we aren't just reselling someone else's hardware.
Dual 9754's are indeed quite nice. ;-)
[0] https://github.com/ROCm/HIPIFY https://github.com/ROCm/HIPIFY
- renewiltord 3y agoThank you for the link and advice. We're using 9684X for the cache. But dual 9754 does sound good!
- latchkey 3y agoOh yea, great chip as well. That cache certainly is expensive! Can I ask... what is the usecase for the cache?
- renewiltord 3y agoWe use the chip general purpose. HFT simulation code, empirically faster. The GPUs are to train a model. Separate use-case, but we use same hardware for both use-cases so that's why the big cache thing.