Micro instance (t1.micro) type is one of the most fashionable and quite acceptable sample types with IT Fellows supported by Amazon EC2. During November 2010, announced the AWS free tier and began offering 750 hours of usage per month free micro instance for the first year, but it is available as an Amazon EBS-backed instances only. You can now start the EC2 Virtual Private Cloud (VPC). AWS is now reaching t1.micro events run through also.
Talking VPC in the technical specifications, Micro instance type is not much power is needed to stimulate weight. Presented in the main memory 613MB Micro instance type. It has burst CPU capacity can be up to 2 Elastic Compute Unit (ECU). That means the CPU performance is not conventional. It is just not enough to run any heavy workload. And yes, the storage can be added via the Elastic Block Storage (EBS) and layers span up to 30GB of free storage when optimizing AMI space.
Best recommended for this type of micro example:
Design AMI can perform to the max. 600 MB Memory Usage
The end of a chronic process using CPU time (for example, cron jobs, daemons) but from the technical specification does not mean Chances Micro totally ineffective. They offer great value in some cases. In this article, I want to share how to get the best out of Amazon EC2 MI.
Optimize Memory Swap – It has nothing to do with Linux-based Micro Sample. By default, there is an exchange type of opportunities configuration space on the first level. I run my Cloud Magic World Website in a MI for a few days. During load the ridge, I had Apache or MySQL server crash unexpectedly. So it only has 613 MB on your opening, you can be sure that you set aside enough disk space to Measure swap.
Auto Out – The Fund
a Cloud auto-scale out. Running a low-end server convoy in parallel more reliable and cost effective in the virtual infrastructure. Appropriate burden-sharing and use cases, works full amount Micro Sample can be cheaper and faster than running the same job at a single large time. The scale out design provides better structural repeatedly fail quickly processing.
Mull Caching – If you are scheduled to host the site, be clear in your mind that this is not very dynamic. Dynamic websites required more CPU power and memory as it approaches each request is processed. Web sites such as blogs and websites direct marketing with some dynamic content is suitable for participants Micro Sample. In addition, consider the cache contents to prevent CPU spikes. For example, if you have a blog or website, you can activate the plug-in cache to improve performance. Many plug-ins are available for free cost.
Select caching by 64-bit – always choose the 64-bit when running. It is reassuring to give a musical performance that is better than the addition of 32-bit. You’ll notice the difference when you run the batch processing associated with large files and processes.
Pull cron job – Many customers run Linux Micro instance to run a cron job and the right of local activities to monitor and manage their entire infrastructure of AWS. If you want to run a cron job, stop all other services running, add a space and drag to exchange examples create a cron job lean and mean machine.