Show HN: I made a calculator to show cost savings of serverless GPUs vs. AWS
1–5 of 5 posts
Re: Show HN: I made a calculator to show cost savings of serverless GPUs vs. AWS
#2Sometimes it's cheaper and more practical to just buy the hardware.
I had a similar issue with a company I worked for before, we had an account on Azure and the machine was expensive but also slow and after 4 months we decided to buy a used server for $1000 and closed the Azure account and never looked back.
Re: Show HN: I made a calculator to show cost savings of serverless GPUs vs. AWS
#3Or you can just buy a GPU instead of renting one out. I have a project where users generate designs for clothing and the mock ups get rendered in 3D on various different models, about 20 variations per design. Instead of paying a monthly bill to some GPU provider forever I instead bought a Nvidia Jetson Nano and set it up as a render server. It constantly looks at it's render queue and renders as needed. It cost me $…
Re: Show HN: I made a calculator to show cost savings of serverless GPUs vs. AWS
#4Or you can just buy a GPU instead of renting one out. I have a project where users generate designs for clothing and the mock ups get rendered in 3D on various different models, about 20 variations per design. Instead of paying a monthly bill to some GPU provider forever I instead bought a Nvidia Jetson Nano and set it up as a render server. It constantly looks at it's render queue and renders as needed. It cost me $…
Do you mind sharing how you ‘deployed’ your own gpu? How did you host this?
Once ready I opened up the render queue page in Chrome on it and as soon as a new job comes in it renders it. It get's it's jobs from a SSE connection. I use Three.js as the 3D library. It works very well now but in the beginning it had some hitches because while the GPU is strong the CPU on the Nano is very weak, so decompressing the models and the initial asset loading where not as fast on beefy modern x86-64 but nothing a few quick optimizations could not fix. The final hurdle was occasionally losing context but I just added a listener for those events and restarted the job if it failed. Another fun solution was checking to see if the image were actually rendered instead of just a transparent PNG by checking the file size of the outputted image, if the image is impossibly small it gets sent back to the job queue.
Re: Show HN: I made a calculator to show cost savings of serverless GPUs vs. AWS
#5depending on usage, you could start saving money over rented GPU time in a single-digit number of weeks.