OVH - Boxes/billing for 2020 (migrate VMs from padthai to paella)
I've been running some numbers re:padthai
and barbecue
hosting. Notes:
-
There are 5 VMs running on these boxes (
test-1
,test-3
,www-test
,www-demo
,botdylan
) -
Currently, padthai goes through
ca.ovh.com
(which allows 1/3/6/12mo arrangements), and bbq goes throughus.ovhcloud.com
(which is strictly month-to-month). -
padthai
bills at a higher rate thanbarbecue
($122/mo vs $99/mo), butbarbecue
is markedly faster thanpadthai
. (25% faster single-thread per Passmark). This is definitely noticeable when running PR tests. (test-1
takes longer to run tests thantest-3
.) -
Being able to prepay reduces the business taxes. I don't know an exact figure, but if we prepay $2k and would have otherwise paid abut 30% * $2k intaxes, then I think it saves ~$600-700.
-
Rough notes/estimation: https://docs.google.com/spreadsheets/d/1FGnxC7Gki_mgU4xNcbKggsy9sglF7EsZCQ87eCRu3k4/edit?usp=sharing
I'm thinking that an optimal path might be to deploy 2x instances of the "Advance-2" (Xeon-E 2136, 64gb, 2x500 SSD) on the "ca.ovh.com" account. This would:
- Enable us to prepay more upfront (reducing taxes)
- Get better CPUs for both boxes (faster cores and more of them) ==> running PRs faster and maybe adding some GL worker capacity?
- Pay lower rate per box ($122+99/mo ==> $97+$97/mo)
- Manage both boxes from the same account (less billing/admin)
- Most of the VM's (
test-1
,www-test
,www-demo
,botdylan
) would still be at OVH in the same CA data-center... so potentially one could keep the IPs and simply move the disk-images?
That saves about $1k for the year on tax+hosting. The main Q is the cost/difficulty of migrating the VMs to new physical boxes. @bgm Do you think this is something we could do easily?
If the labor is a problem, then a fallback option would be to prepay padthai. (There's no technical work for anyone, and we get some of the tax savings, but gotta stick it out on older CPU.)