Thanks for the feedback. Multi-loud is currently implemented for AWS and a few Rackspace instances. The ffmpeg report should be fixed now - a small bug on our p

Thanks for the feedback. Multi-loud is currently implemented for AWS and a few Rackspace instances. The ffmpeg report should be fixed now - a small bug on our part in the publicly visible reports. We are working with several cloud providers as well as HPC system providers to get them integrated, including SoftLayer. If you could connect us with someone at GCE to get this rolling that would be of course appreciated. Regarding your comments on instances these are very valid, and the filters you suggest would be indeed very useful. Presently, if an instance runs out of memory for a particular benchmark it returns a failed code and will be excluded from the Profiler results. On the t2.* instances absolutely agreed that they are good for bursty loads, but once the credits are depleted then the performance drops off the cliff. For this there are two potential solutions: First, a long running workload will expose this drop off, i.e something that runs for more than ~30 minutes on a t2.micro. Another way, would be for us the benchmark a credit depleted instances to show the performance delta - we do have that on the schedule so that people can understand the performance implications.