Sterling Baird
My feedback
1 result found
-
10 votes
An error occurred while saving the comment Sterling Baird supported this idea ·
1 result found
Please sign in to leave feedback
Please sign in to leave feedback
No results.
Clear search results
I accidentally wasted ~$150 in ~30 minutes because I used `find_one` (without an index) in a function that was running many instances in a high-performance computing environment. As someone using this for academic research as a student, not for business, it would have been really nice if I could have set some kind of cap or throttle. Had things gone slightly differently, this could have been much worse. I happened to notice the icon in the corner with the default alert of 1 million RPU/s. This led to me digging a bit deeper into the RPU pricing model trying to resolve the difference in how units are presented in the documentation vs. the monitoring page (M vs. MM, both referring to million apparently). This led me to do some rough calculations which quickly led me to stop the HPC runs that were causing the high usage. Had I left it running overnight instead of catching it after ~30 minutes, the situation would have been worse.