3 ms·
The author of the original article is, at least for some of his tests: “(on an 8-core EC2 instance, c1.xlarge running Xen)”
by guan 15y ago
The author of the original article is, at least for some of his tests: “(on an 8-core EC2 instance, c1.xlarge running Xen)”
- justincormack 15y agoYeah, true, rereading it he is not clear about whether he has run the software on xen on the same box he ran raw on, although it is implied. It is a very different question on EC2.
- cgbystrom 15y agoI've tried it on variety of different servers/hardware using both my server+apachebench and netperf as benchmarking tools. * On EC2 I've tried the c1.xlarge and the giant cc1.4xlarge. With cc1.4xlarge, I saw maybe a ~10% increase accept() rate. * Two separate, virtualized servers at the office. * A private, virtualized server on Rackspace was briefly tested as well. A compilation of netperf results are available at https://gist.github.com/985475 https://gist.github.com/985475
- bigiain 15y agoI doubt it'll reveal anything super useful, but running your tests on a single-tenant EC2 instance could add an extra datapoint. I suspect it'll only reveal that the problem _isn't_ due to EC2/Xen swapping your virtualized machine out. (assuming you haven't tried it already...)