Fault domain on Oracle is quite similar to the concept of Zones on Amazon Lightsail.
Basically, within the same location, they split into several separate areas. The idea is to avoid the situation where all the customer’s resources are down if one Zone fails, by having other Zones still working.
Usually, VPS providers will automatically manage this. If you have a VPS in Zone A, when you create a new VPS, the default location will be B or C.
I think the best idea of this is to use different Zones in case of system upgrade, power outage, earthquake, tsunami or something like that. Amazon will switch to other Zones to ensure the continuity of service.
Zone A, B, C are names that Amazon assigns to each customer’s account, not the common names of the whole system. In other words, Zone A for me may be Zone B for another customer.
On Oracle, Fault Domain is an option in the Placement tab, which is hidden by default. Oracle will automatically choose the Fault Domain area.
Usually I see that their three locations have similar speeds, so I don’t care much. Partly because on Oracle, creating a free VPS at Singapore location is hard (mostly using auto tools), who has time to choose the area.
The funny story is that I often test some server setup tools, so I create, delete, and reinstall new ones constantly. Today I wrote an article about Reinstall OS, so I speedtest a lot. Suddenly I see a new VPS with speed only about 100MB when going to US, ping back to Vietnam up to 100ms, even ping in Singapore up to 6x, while normally ping local only up to 2ms at most.
Fortunately, I use Pay As You Go account, so I can create and delete VPS quite comfortably, so I can check this out.
Ping to a VPS file.xtapo.org then see 3x-4xms, while new VPS ping all 100ms, check and see it all comes from Fault Domain: FD-1. Look back at file.xtapo.org then it is at Fault Domain: FD-3.
Try creating a new VPS, manually select Fault Domain: FD-3 then see ping 3x, 4x as usual.
It is very likely that because of this, the tests on Caddy Http Cache in the LCMP article encountered errors. That day I created a new VPS, probably it flew straight into Fault Domain: FD-1 which was having network problems. The speed dropped low, so when loading 100 images at once, it was quite bad. Today I tried again and saw it better. Not as fast as Nginx cache but not as bad as the other day.
Simply put if you create a new VPS on Oracle and see it slow down, change Fault Domain to another location.
If the cluster you are using runs well for a while and then suddenly has network problems and high ping then try creating a new VPS in another Fault Domain and see if it improves. If you have time you can move back there but wait for Oracle to fix it don’t know when
bookmarked!!, I like your site!