Good Day,
I would like to check what is the meaning of 'Utilisation' in Amazon EC2. If my java server is running but 'IDLE' and using less than 2 percent of CPU for example 24/7 for a month..how much Utilisation is that?
I am using this calculator
http://calculator.s3.amazonaws.com/calc5.html
Would appreciate if someone could help me clarify. I have done quite a bit of search for this term but I have come up with nothing.
You are being billed for your instance as long as its in a running state. It doesn't matter how much CPU usage you have.
Related
I have a requirement that says if I have the CPU Utilization of 70% of one EC2 instance It should be scaled up and if I have the CPU Utilization of 30% and at least two EC2 instances it should be scaled down. This is working fine, I can scale up and scale down as it is supposed to be.
But for scenarios in which I have at least two EC2 instances, and one has CPU Utilization of 70% and another one has 30% I should migrate the CPU Workload from the instance with 70% to the one with 30%.
Does anyone know how can I do this using boto3? I've read the EC2 documentation but did not find anything related to this kind of workload migration.
Does anyone know how can I do this using boto3?
You can't do this in general and that's why you did not find anything about this. This is not how EC2 Autoscaling works, assuming that you are using the scaling as its not stated in your question.
You would have to develop your own, custom solution for such a requirement. And this depends on exactly what is your "workload". It is also not explained in your question so its difficult to even begin recommending something.
I just did coding a service with all working functionality, now I am starting to worry about performance. without any change to current code, I get around 500-600 tps. And then I started to enhance my code and get around 1100-1200 tps(just code without increasing vm specs). Is this enough? my answer is "I am not sure". can anybody give me a clue how much tps is ideally for a service node?
PS : it runs on 2 core and 2 GB ram VM. service that I worked on is CRUD with medium logic calculation in it, using golang
It is related with your rps(request per second) check out several simulation in link below
What's the "average" requests per second for a production web application?
Personally I think over 1000 tps for a service is already good.
I'm based in the UK, as are all users of my web app, and currently host in the EU-West region. The US-East region is quite a bit cheaper and I'm using a service from another company that locate their servers in the US-East region (meaning that I'll have data transfer costs between regions if I kept things in the EU). Has much of a speed difference am I likely to see between the two?
(I could do a test myself but I'm hoping someone else has already done it :) )
I'd appreciate insights that anyone has. Thanks in advance
I found a nice service which compares the speed and latency of different clouds and different regions:
http://cloudharmony.com/speedtest
You can pick only the amazon services and test all regions.
Speed within Availability zones is very impressive. When you start talking about across continents you're going to get some lag and much less bandwidth. I think it would depend what you're passing over the network whether it would work in your case or not. However, to answer your question there is a very large difference in speed.
I'm writing a ruby program that need raw cpu power (I know ruby is a very bad choice for this!).. but I don't have a powerful computer, so I wanted to rent something online that you pay per hour..
Any idea? Something simple to use yet very powerful, with multiple cores. I took a look at amazon ec2, that's a possibility. Anything else, more CPU oriented?
As far as on-demand compute power, Amazon's EC2 is a good choice. You can either pay market rates or you can go to their special discount spot market which is similar, but your instance can and will be terminated without warning when demand picks up again.
It's best to have a system that either uses a persistent EBS drive to save results, or saves them to something like S3 frequently.
If you can parallelize your processing, try and split it across the most cost-effective instance type instead of having to pay a premium for a single instance. For example, the XL Hi-CPU On-Demand Instance gives you 20 compute units for $0.68/hr. compared with the 4XL Cluster Compute Instance which is only 33.5 for $1.60/hr.
Remember that a single Ruby process can only use one CPU core unless you're using a combination of JRuby and threads. You will need to support multiple processes in order to make full use of the machine if this is not the case.
SimpleWorker - I think it's more simpler then EC2.
I am looking at the pricing of various cloud computing platforms, particularly Amazon's EC2, and a lot of the quotes are based on a unit called an Instance-Hour.
I am trying to get a handle on the exact definition of an instance-hour to better compare the costs of continuing to host a web-application versus putting it out on the cloud.
(1) Does it correspond to any of the Windows performance counters in such a way that I could benchmark our current implmentation and use it in their pricing calculators?
(2) How does a multi-processor instance figure into the instance-hour calculation?
An instance hour is simply a regular hour where the instance was available to you, wether you used it or not. Amazon has priced their different types of instances differently, so you pay for the type of resource you are getting, not how much you use it.
So... 1. No, it's just a regular hour. 2. It doesn't, it's already factored into the price you pay for the instance pr hour.
Note also that instance hours are billed rounded up (for Amazon EC2). So starting up an instance and immediately shutting it down again incurs the cost of 1 instance hour.
if you plan to start/stop the AWS EMR cluster rapidly within a single hour, and you want to avoid being billed for a full hour each time you do so, then
start the cluster with the --alive argument from cli, which means to leave it running.
then rapidly add steps to the same cluster, instead:
http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/AddingStepstoaJobFlow.html
Don't forget to stop the cluster when you're done! :)