Re: AWS usage per group
Hi - > http://debuginfod1.aws.centos.org/ uses io1 type volume. This is suboptimal > as io2 is better. But from monitoring the machine does not utilize the IOPS > and the price for this volume is ten times more than gp3 which would provide > equivalent performance Yes, this service does not require top performance storage, heck not even SSD. Please feel free to do whatever conversion is possible. - FChE ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS usage per group
Dne 31. 10. 23 v 12:30 Frank Ch. Eigler napsal(a): Hi - http://debuginfod1.aws.centos.org/ uses io1 type volume. This is suboptimal as io2 is better. But from monitoring the machine does not utilize the IOPS and the price for this volume is ten times more than gp3 which would provide equivalent performance Yes, this service does not require top performance storage, heck not even SSD. Please feel free to do whatever conversion is possible. Ok. I converted it to GP3. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS usage per group (March)
On Tue, Apr 02, 2024 at 01:21:55AM +0200, Miroslav Suchý wrote: > Here comes January edition of resources running in AWS. It's a snapshot of > resources running today. > > Per request of Miro Vadkerti I grouped it by (FedoraGroup, region, > ServiceName). I will try to make it more compact next time, but giving up > now as it already cost me half of the night. Nice improvement. I like it. :) kevin signature.asc Description: PGP signature -- ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS usage per group (April)
Dne 02. 05. 24 v 7:25 dop. Miroslav Suchý napsal(a): Here comes April edition of resources running in AWS. It's a snapshot of resources running today. I had a bug in script and size of volumes were incorrectly calculated. Here is fixed version: FedoraGroup: abrt Region: us-east-1 Service Name: Instance Type: t3a.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 10 GiB FedoraGroup: centos Region: ap-south-1 Service Name: Instance Type: t3.2xlarge - Count: 3 Instance Type: t3.large - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4570 GiB Region: eu-central-1 Service Name: Instance Type: t2.large - Count: 1 Instance Type: r5b.8xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 1 Volume Type: gp3 - Total Size: 13170 GiB Region: us-west-2 Service Name: Instance Type: m6i.2xlarge - Count: 2 Instance Type: t3.small - Count: 1 Instance Type: t3.xlarge - Count: 1 Volume Type: gp3 - Total Size: 13145 GiB Region: af-south-1 Service Name: Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4050 GiB Region: eu-west-3 Service Name: Instance Type: t2.2xlarge - Count: 1 Instance Type: t3a.xlarge - Count: 1 Instance Type: t2.large - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t3.large - Count: 1 Volume Type: gp3 - Total Size: 2917 GiB Region: eu-west-2 Service Name: Instance Type: t2.large - Count: 1 Instance Type: t3a.large - Count: 2 Instance Type: r5a.8xlarge - Count: 1 Instance Type: t3.large - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t2.medium - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 26300 GiB Region: eu-west-1 Service Name: Instance Type: t2.medium - Count: 4 Instance Type: t2.xlarge - Count: 3 Instance Type: t2.large - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: t3.medium - Count: 2 Volume Type: gp3 - Total Size: 584 GiB Region: ap-northeast-1 Service Name: Instance Type: c6g.2xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 8070 GiB Region: sa-east-1 Service Name: Instance Type: c6g.4xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4250 GiB Region: ap-southeast-1 Service Name: Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4050 GiB Region: ap-southeast-2 Service Name: Instance Type: m6i.2xlarge - Count: 2 Volume Type: gp3 - Total Size: 8100 GiB Region: us-east-1 Service Name: Instance Type: t3.xlarge - Count: 2 Instance Type: t2.xlarge - Count: 1 Volume Type: gp3 - Total Size: 26350 GiB Region: us-east-2 Service Name: Instance Type: t2.2xlarge - Count: 1 Instance Type: m5a.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 4 Instance Type: t3a.large - Count: 1 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t2.large - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: m4.2xlarge - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 50090 GiB FedoraGroup: Not tagged Region: ap-south-1 Service Name: # of AMIs: 1306 Region: eu-south-1 Service Name: # of AMIs: 102 Region: il-central-1 Service Name: # of AMIs: 85 Region: ca-central-1 Service Name: # of AMIs: 1320 Region: eu-central-1 Service Name: # of AMIs: 1342 Region: us-west-1 Service Name: # of AMIs: 1348 Region: us-west-2 Service Name: # of AMIs: 1343 Region: af-south-1 Service Name: # of AMIs: 104 Region: eu-north-1 Service Name: # of AMIs: 103 Region: eu-west-3 Service Name: # of AMIs: 104 Region: eu-west-2 Service Name: # of AMIs: 1358 Region: eu-west-1 Service Name: # of AMIs: 1312 Region: ap-northeast-2 Service Name: # of AMIs: 1307 Region: me-south-1 Service Name: # of AMIs: 102 Region: ap-northeast-1 Service Name: # of AMIs: 1345 Region: sa-east-1 Service Name: # of AMIs: 1324 Region: ap-east-1 Service Name: # of AMIs: 103 Region: ap-southeast-1 Service Name: # of AMIs: 1330 Region: ap-southeast-2 Service Name: # of AMIs: 1321 Region: us-east-1 Service Name: Instance Type: c6a.2xlarge - Count: 4 Volume Type: gp3 - Total Size: 2882 GiB # of AMIs: 1588 Region: us-east-2 Service Name: Instance Type: c5.2xlarge -
Re: AWS usage per group (July)
Dne 02. 08. 24 v 3:18 odp. Miroslav Suchý napsal(a): Here comes July edition of resources running in AWS. It's a snapshot of resources running today. I spent some today hacking AWS pricing code. And ... it is my pleasure to show you the same report with dollars included. It counts instance price, volume price (including provisioned IOPS). It does not count the price of Snapshots and AMIs yet. And the price does not take in accounts reserved instances or spot requests (e.g., both heavily used by Copr) To save you the digging here is the summary: FedoraGroup: qa - PriceSum: $72689 FedoraGroup: centos - PriceSum: $31226 FedoraGroup: copr - PriceSum: $18302 FedoraGroup: ci - PriceSum: $13992 FedoraGroup: infra - PriceSum: $10383 FedoraGroup: Not tagged - PriceSum: $7508 FedoraGroup: pyai - PriceSum: $3712 FedoraGroup: respins - PriceSum: $702 FedoraGroup: centos-stream-osci - PriceSum: $571 FedoraGroup: logdetective - PriceSum: $481 FedoraGroup: min - PriceSum: $471 FedoraGroup: CentOS - PriceSum: $306 FedoraGroup: abrt - PriceSum: $236 FedoraGroup: centos-stream-build - PriceSum: $8 FedoraGroup: garbage-collector - PriceSum: $0 And now the full report: FedoraGroup: pyai - PriceSum: $3712 Region: us-east-1 Service Name: N/A - PriceSum: $3712 Instance Type: t2.large - Count: 1 - Price: $68 Instance Type: i3.16xlarge - Count: 1 - Price: $3644 FedoraGroup: centos-stream-osci - PriceSum: $571 Region: ca-central-1 Service Name: N/A - PriceSum: $571 Instance Type: m5d.large - Count: 5 - Price: $460 Instance Type: t2.micro - Count: 1 - Price: $9 Volume Type: gp3 - Total Size: 36 GiB - Price: $102 FedoraGroup: CentOS - PriceSum: $306 Region: us-east-2 Service Name: N/A - PriceSum: $306 Instance Type: m5.2xlarge - Count: 1 - Price: $280 Volume Type: gp3 - Total Size: 140 GiB - Price: $26 FedoraGroup: infra - PriceSum: $10383 Region: ap-south-1 Service Name: N/A - PriceSum: $163 Instance Type: c5d.xlarge - Count: 1 - Price: $145 Volume Type: gp3 - Total Size: 8 GiB - Price: $18 Region: eu-central-1 Service Name: N/A - PriceSum: $2960 Instance Type: c5d.xlarge - Count: 1 - Price: $162 Instance Type: c5n.2xlarge - Count: 1 - Price: $359 Instance Type: m5.xlarge - Count: 1 - Price: $168 Instance Type: m6gd.4xlarge - Count: 1 - Price: $637 Volume Type: gp3 - Total Size: 16223 GiB - Price: $1634 Region: us-west-1 Service Name: N/A - PriceSum: $245 Instance Type: t3.medium - Count: 1 - Price: $36 Instance Type: t2.xlarge - Count: 1 - Price: $161 Volume Type: gp3 - Total Size: 120 GiB - Price: $48 Region: us-west-2 Service Name: N/A - PriceSum: $844 Instance Type: m5.large - Count: 3 - Price: $210 Instance Type: m6g.large - Count: 1 - Price: $56 Instance Type: c5n.2xlarge - Count: 1 - Price: $315 Instance Type: c6gd.xlarge - Count: 1 - Price: $112 Volume Type: standard - Total Size: 100 GiB - Price: $5 Volume Type: gp3 - Total Size: 700 GiB - Price: $146 Region: af-south-1 Service Name: N/A - PriceSum: $0 Instance Type: c5d.xlarge - Count: 2 - Price: $0 Volume Type: gp3 - Total Size: 25 GiB - Price: $0 Region: eu-west-2 Service Name: N/A - PriceSum: $187 Instance Type: c5d.xlarge - Count: 1 - Price: $168 Volume Type: gp3 - Total Size: 20 GiB - Price: $19 Region: eu-west-1 Service Name: N/A - PriceSum: $3259 Instance Type: m4.10xlarge - Count: 2 - Price: $3241 Volume Type: gp3 - Total Size: 20 GiB - Price: $18 Region: ap-northeast-2 Service Name: N/A - PriceSum: $417 Instance Type: c5n.2xlarge - Count: 1 - Price: $356 Volume Type: gp3 - Total Size: 290 GiB - Price: $61 Region: sa-east-1 Service Name: N/A - PriceSum: $955 Instance Type: c5.2xlarge - Count: 1 - Price: $383 Instance Type: c5n.2xlarge - Count: 1 - Price: $485 Volume Type: gp3 - Total Size: 200 GiB - Price: $87 Region: ap-southeast-1 Service Name: N/A - PriceSum: $774 Instance Type: c5n.2xlarge - Count: 2 - Price: $724 Volume Type: gp3 - Total Size: 150 GiB - Price: $50 Region: us-east-1 Service Name: N/A - PriceSum: $421 Instance Type: t3.medium - Count: 1 - Price: $30 Instance Type: t3.small - Count: 1 - Price: $15 Instance Type: c5.xlarge - Count: 1 - Price: $124 Instance Type: t2.medium - Count: 2 - Price: $68 Volume Type: gp3 - Total Size: 425 GiB - Price: $184 Region: us-east-2 Service Name: N/A - PriceSum: $158 Instance Type: c5d.large - Count: 1 - Price: $70 Instance Type: t2.micro - Count: 1 - Price: $8 Instance Type: t3.medium - Count: 1 - Price: $30 Volume Type: gp3 - Total Size: 63 GiB - Price: $50 FedoraGroup: Not tagged - PriceSum: $7508 Region: us-west-2 Service Name: N/A - PriceSum: $548 Instance Type: c6i.2xlarge - Count: 2 - Price: $496 Vol
Re: AWS usage per group (July)
On Sat, Aug 03, 2024 at 12:44:17PM GMT, Miroslav Suchý wrote: > Dne 02. 08. 24 v 3:18 odp. Miroslav Suchý napsal(a): > > > > Here comes July edition of resources running in AWS. It's a snapshot of > > resources running today. > > > > I spent some today hacking AWS pricing code. And ... it is my pleasure to > show you the same report with dollars included. > > It counts instance price, volume price (including provisioned IOPS). It does > not count the price of Snapshots and AMIs yet. And the price does not take > in accounts reserved instances or spot requests (e.g., both heavily used by > Copr) > > To save you the digging here is the summary: > > FedoraGroup: qa - PriceSum: $72689 Wow... I guess this is the openqa test/development setup in aws. Some of those instances are... really really large. I guess I understand why they might need to be thought. > FedoraGroup: centos - PriceSum: $31226 > FedoraGroup: copr - PriceSum: $18302 > FedoraGroup: ci - PriceSum: $13992 > FedoraGroup: infra - PriceSum: $10383 > FedoraGroup: Not tagged - PriceSum: $7508 > FedoraGroup: pyai - PriceSum: $3712 > FedoraGroup: respins - PriceSum: $702 > FedoraGroup: centos-stream-osci - PriceSum: $571 > FedoraGroup: logdetective - PriceSum: $481 > FedoraGroup: min - PriceSum: $471 > FedoraGroup: CentOS - PriceSum: $306 > FedoraGroup: abrt - PriceSum: $236 > FedoraGroup: centos-stream-build - PriceSum: $8 > FedoraGroup: garbage-collector - PriceSum: $0 This is only ec2 resources right? Not cloudfront or other things? Thanks for crunching all these numbers. kevin signature.asc Description: PGP signature -- ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS usage per group (July)
Dne 04. 08. 24 v 5:28 odp. Kevin Fenzi napsal(a): This is only ec2 resources right? Not cloudfront or other things? Just instance cost, Volume and IOPS cost. No Snapshots, no CloudFront, no EllasticIP, no S3 cost I want to add Snapshots cost in near future. And count spot prices for Spot EC2 instances. CloudFront would be hard to split per FedoraGroup. And not sure if it that would bring any beneficial information. Cost of CloudFront as total is already visible on invoice. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS usage per group (July)
On Sun, Aug 04, 2024 at 09:35:26PM GMT, Miroslav Suchý wrote: > Dne 04. 08. 24 v 5:28 odp. Kevin Fenzi napsal(a): > > This is only ec2 resources right? Not cloudfront or other things? > > Just instance cost, Volume and IOPS cost. > > No Snapshots, no CloudFront, no EllasticIP, no S3 cost > > > I want to add Snapshots cost in near future. And count spot prices for Spot > EC2 instances. > > CloudFront would be hard to split per FedoraGroup. And not sure if it that > would bring any beneficial information. Cost of CloudFront as total is > already visible on invoice. Yeah, but perhaps per distribution could be useful to know what things are most heavily used, but I am not sure what we could do with that info in the end so perhaps you're right. kevin signature.asc Description: PGP signature -- ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
