I tried to do tpcc-mysql benchmark for Amazon RDS. Before do that, did the same test for EC2 small instance.
From EC2 small instance to small. Fedora8 and MySQL 5.0.45. Default configuration. (no change for a my.cnf; innodb_buffer_pool_size = 8388608)
# mysql -h domU-12-31-39-06-7C-86.compute-1.internal -u mymasteruser -p mysql> grant all privileges on tpcc.* to tpcc@'%' identified by 'hogehoge'; mysql> create database tpcc; # mysql -u tpcc -p -h domU-12-31-39-06-7C-86.compute-1.internal tpcc < create_table.sql # mysql -u tpcc -p -h domU-12-31-39-06-7C-86.compute-1.internal tpcc < add_fkey_idx.sql # ./tpcc_load domU-12-31-39-06-7C-86.compute-1.internal tpcc tpcc hogehoge 10 # ./tpcc_start domU-12-31-39-06-7C-86.compute-1.internal tpcc tpcc hogehoge 10 3 60 60 527.000 TpmC # ./tpcc_start domU-12-31-39-06-7C-86.compute-1.internal tpcc tpcc hogehoge 10 6 60 180 560.667 TpmC
Changed to innodb_buffer_pool_size = 1336934400. (same as RDS small instance) Drop database, and restore. Then,
# ./tpcc_start domU-12-31-39-06-7C-86.compute-1.internal tpcc tpcc hogehoge 10 6 60 180 2358.667 TpmC
From EC2 small instance to RDS small instance. (MySQL 5.1.38)
# ./tpcc_load myinstance.cpxpgflqvl3w.us-east-1.rds.amazonaws.com tpcc tpcc hogehoge 10
There will be an error "server phrase is too long". Use IP address.
# ./tpcc_start 10.210.155.149 tpcc tpcc hogehoge 10 6 60 180 2437.000 TpmC
This is a pretty rough benchmark, but I can say EC2 small instance and RDS small instance have the same performances as CPU and memory are the same spec. RDS is about 30% expensive. (EC2=$0.085, RDS=$0.11/h)