News for hackers. Stuff that matters.
Re:The ominous opacity of the AWS bill – a cautionary tale by murphy214 on Tuesday December 03, 2019 @03:44PM (#21696502)
I would love to have tooling for what AWS consider an IO/OP, I've read the documentation quite a few times and I think I get it, basically every 256 kb read or reads under that but at what level of the stack is that considered from. I tried to find metrics/tools of how to count it as AWS counts but couldn't really find much.

The reason being I have a library that reads a file in an x-size buffer along a file iteratively using bufio in go, and I'm not exactly sure what optimizations are happening that I can't see, and at some points I'm incrementing a file a byte at a time, thats by definition an IO/OP I think (super inefficient). Unfortunately a lot of the cloud metrics don't give you enough granularity or quick feedback to optimize.

Re:The ominous opacity of the AWS bill – a cautionary tale by wmf on Tuesday December 03, 2019 @04:57PM (#21697216)
I would bet an EBS IOP is the same as a Linux block device IOP which you can monitor with iostat.
Re:The ominous opacity of the AWS bill – a cautionary tale by NovemberWhiskey on Tuesday December 03, 2019 @04:47PM (#21697113)
Is this in the context of an EBS volume?