ec2instances.info
ec2instances.info copied to clipboard
vantage-sh
Individual Instance Inspection
There's a need to be able to trace the data and rendering for just 1 instance type to more rapidly fix data issues that occur for that instance. The following instances have had issues reported:
| Instance | Issue |
|---|---|
| mac1.metal | billing is a 24 hour period |
| ra3.16xlarge | memory and node range stats should be different |
| cache.t4g.micro | add cpu credits |
| p4de.24xlarge | network performance column doesn't sort properly |
| t3a.large | add hibernation stats |
| m5d.large | add number of ENIs |
| db.r6i.2xlarge | pricing is off by $1k/mo |
| ra3.xplus | network details |
| r6i.2xlarge | max pods on EKS |
| g5.12xlarge | compute capability is 8.6 |
| db.r6g.16xlarge | RDS max throughput |
| t3.large | Intel extensions such as AVX512 |
| trn1.32xlarge | missing GPU info #689 |
| r6i.4xlarge | wrong CPU speed #688 |
| trn1.32xlarge | network data inconsistency #686 |
| hpc6a | not showing in oregon region #614 |
| m5.2xlarge | incorrect rate in signapore #604 |
| m6g.medium | clock speed is unknown #542 |
This should be a command line switch that can be added to the build invoke set of scripts. When specified, the code should only get pricing data for the one instance. Raw pricing data from AWS should be printed to the console at every step. The final data that will be rendered onto the page should be printed as well. Since running the entire scraping process can take up to 10 minutes, this will significantly shorten development cycles.
This is most useful for EC2 which is the longest script that needs to run - scrape.py.
| Instance | Issue |
|---|---|
| t3a.smal | Baseline vCPU / burstable credits #596 |
| r7g.12xlarge | r7g.12xlarge says 48 vcpus and 384GB ram but it is 192GB ram on this page https://aws.amazon.com/ec2/instance-types/m7g/. Also, the r7g.16xlarge and r7g.metal say 512GiB ram here, but the page says 256GiB |
| db.t4g.medium | I don't see db.t4g available in the UAE region on the "Purchase reserved DB instances" page. But on your page it seems to indicate it is available. |
| cache.t4g.micro | baseline bandwidth #617 |
| i3p.16xlarge | not available in us-east-1 so not shown |
| c6gn.metal | not available in us-east-1 so not shown |