summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorSnapshot Automation Bot <_@users.noreply.github.com>2024-11-14 08:13:06 +0000
committerSnapshot Automation Bot <_@users.noreply.github.com>2024-11-14 08:13:06 +0000
commit7e3aaa24142ef6376e45b6cc2d881c71a6b4a534 (patch)
treeeb1b5995c14d202e647240fd51bb3e83f876f702 /README.md
parenteab8bc1f6abb1cc407974204dbc7bc5fcf455e94 (diff)
Data snapshot commit
Signed-off-by: Snapshot Automation Bot <_@users.noreply.github.com>
Diffstat (limited to 'README.md')
-rw-r--r--README.md59
1 files changed, 59 insertions, 0 deletions
diff --git a/README.md b/README.md
new file mode 100644
index 00000000..9b050dab
--- /dev/null
+++ b/README.md
@@ -0,0 +1,59 @@
+# 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: 2024-11-14T08:13:06.147800
+
+| AWS Region | Avg Latency | Least |
+| - | - | - |
+| af-south-1 | 0.881 | |
+| ap-east-1 | 0.837 | |
+| ap-northeast-1 | 0.665 | |
+| ap-northeast-2 | 0.771 | |
+| ap-south-1 | 0.853 | |
+| ap-southeast-1 | 0.930 | |
+| ap-southeast-2 | 0.809 | |
+| ca-central-1 | 0.127 | |
+| eu-central-1 | 0.417 | |
+| eu-north-1 | 0.460 | |
+| eu-south-1 | 0.441 | |
+| eu-west-1 | 0.323 | |
+| eu-west-2 | 0.364 | |
+| eu-west-3 | 0.378 | |
+| me-south-1 | 0.763 | |
+| sa-east-1 | 0.509 | |
+| us-east-1 | 0.063 | 1 |
+| us-east-2 | 0.136 | |
+| us-gov-east-1 | 0.122 | |
+| us-gov-west-1 | 0.370 | |
+| us-west-1 | 0.302 | |
+| us-west-2 | 0.337 | |
+