.png)
.svg)
.svg)
.svg)
.svg)
Cloud Mercato tested CPU performance using a range of encryption speed tests:
Cloud Mercato's tested the I/O performance of this instance using a 100GB General Purpose SSD. Below are the results:
I/O rate testing is conducted with local and block storages attached to the instance. Cloud Mercato uses the well-known open-source tool FIO. To express IOPS the following parametersare used: 4K block, random access, no filesystem (except for write access with root volume and avoidance of cache and buffer.
.png)
Just did a quick test. It booted up in about 11s vs around 19s for Xen. I did notice that it took a while for the status check to go green though. There was a warning message saying that it couldn't connect to the instance. I was able to SSH just fine though.
We are currently running c5n.9xl hosts (which are enormous). Using those certainly made a difference, but looking at their logs in AWS Console they are clearly under utilised.
We are currently running c5n.9xl hosts (which are enormous). Using those certainly made a difference, but looking at their logs in AWS Console they are clearly under utilised. I guess we are going to have to start to experiment with using fleets of more, but smaller, hosts to see how things go. It's a pity Splunk don't have a recommended machine size if literally all you are doing is forwarding - we need to run the http collector and the AWS Add-on to pull some S3 info, but even they are basically just acquiring and forwarding. No explicit indexing, no props and transforms, etc...
Ah, I'm having the same problem! Which C series did you pick?
Ah, I'm having the same problem! Which C series did you pick?
Ah, I'm having the same problem! Which C series did you pick?
.svg)
.svg)
%201.svg)
%202.svg)