Usually there are software issues (most commonly, no, not enough or plainly wrong db indexes being the #1 top scorer) which drive rds bills to scary height for no reason at all, but the low hanging fruit is unused cloud 'stuff'.
Usually there are software issues (most commonly, no, not enough or plainly wrong db indexes being the #1 top scorer) which drive rds bills to scary height for no reason at all, but the low hanging fruit is unused cloud 'stuff'.
They had some digging about, and it turned out that most of the FAANG guys would just write a test bit every XXX-1 sec. to keep the disk spinning. As it improved their internal metrics on 'up time' or whatever else they thought was important. So silly.
So, the manufacturer then wrote code to deal with that code to try to save the bearings. And soon enough that code was discovered, and more complicated code was made to keep the disk spinning no matter what.
And back and forth until my buddy retired and stopped caring about this strange little 'arms race'. I suppose it's still going on though.
I don't know if 1B is a reasonable goal, but Twitter's previous leadership was so incompetent that I wouldn't be surprised. Maybe even more is possible.
Sorry for not being clear and thanks for explaining.
An index isn't free so you can impact the write performance, depending on the workload and usecases slower writes could have more of an impact than faster reads.
But even in a read heavy application it's possible that your databases query planner is "tricked" into using a specific index which can actually be slower than another (or even none) so you should always measure the impact that adding an index can have on your application.