diff options
Diffstat (limited to 'README.skel.md')
| -rw-r--r-- | README.skel.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/README.skel.md b/README.skel.md new file mode 100644 index 00000000..5902d2e6 --- /dev/null +++ b/README.skel.md @@ -0,0 +1,35 @@ +# Github Actions Metrics +Information on Github hosted runners like the Azure region they run on is +necessary info when optimising CD/CI pipelines(especially network latencies and +route path bandwidth). Github does not disclose it so I did it myself. + +Using this info, place the resources(DB, object storage, other instances) near +the runners are usually run. + +A few pieces of info I could gather online: + +- Azure doesn't provide a list of VM service endpoints like AWS +- Github-hosted Actions runners are actually Azure VMs (surprisingly, not in a + container) +- Github is hosted in the data centre somewhere in the US, probably in the same + data centre where Azure is present + +Microsoft definitely has more points of presence than any other cloud service +providers, but there's no official list of data center endpoints to ping. If you +look at the map, + +<a href="https://aws.amazon.com/about-aws/global-infrastructure/regions_az/"> +<img src="image.png" style="width: 500px;"> +</a> +<a href="https://datacenters.microsoft.com/globe/explore"> +<img src="image-1.png" style="width: 500px;"> +</a> + +they're close enough. For most devs, all that matters is probably how close +their S3 buckets are to the Github Actions runners. Some AWS and Azure regions +are under the same roof, but then again, no official data. + +## DATA +Updated: %%UPDATED_TS%% + +%%TABLE%% |