# Benchmarking FoundationDB on AWS

**URL:** <https://forums.foundationdb.org/t/benchmarking-foundationdb-on-aws/410>\
**Category:** Using FoundationDB\
**Created:** [May 14, 2018, 9:55am UTC](https://forums.foundationdb.org/t/benchmarking-foundationdb-on-aws/410 "2018-05-14T09:55:57Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ajbeamon](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/ajbeamon/32/13_2.png) [@ajbeamon](https://forums.foundationdb.org/u/ajbeamon)\
**Post date:** [May 14, 2018, 4:45pm UTC](https://forums.foundationdb.org/t/benchmarking-foundationdb-on-aws/410/5 "2018-05-14T16:45:58Z")

</div>

I don’t know the exact details of the test that was run for this, though someone else here may. I can say, though, that the test used our built-in performance testing capabilities. Evan posted a summary for how to use them in this [forum post](https://forums.foundationdb.org/t/ann-benchmark-foundationdb-with-go-ycsb/318/3). The test that was run in the scaling benchmark was probably the RandomReadWrite test linked to by Evan, but with some different parameters. If you go this route, you’ll want to make sure to have sufficient clients (i.e. the `test` class processes) to saturate the cluster if you’re trying to get a sense for cluster throughput.

---

_[View the full topic](https://forums.foundationdb.org/t/benchmarking-foundationdb-on-aws/410)._