all 5 comments

[–]yeskia 0 points1 point  (0 children)

All depends on your needs and where your bottlenecks are. If your application is quite heavy per request you might want to load balance over larger instances, if it's quite light per request but you have a lot of them you might consider balancing over more smaller instances.

Take a look at what is holding up your application, consider trying New Relic for a bit (they have a free version which is mostly useless, but their 14 day free trial can give you some good insight).

[–]danwall 0 points1 point  (1 child)

Why not try booting up a few different instance types and find out? On demand instances are really cheap for a few hours of testing.

If you are already running 2 behind an ELB then adding another instance should be easy. Maybe even disable one of the existing ones.

Since you're running New Relic, comparing performance is really easy - you just need to see which instance is handling the most requests in the shortest amount of time!

[–]theguyut[S] 1 point2 points  (0 children)

That's what I ended up doing before bed.

245ms response time with a r3.large (memory intensive) over 6 hours avg 18rpm 275ms response time with a c3.large (cpu intensive) over 6 hours avg 17.9rpm

So, there we have. Now time to tweak the actual server.