Update 11 Aug 2017: The T1.micro is an example of the previous generation and has been replaced by the t2.micro, which has a better performance profile. See T2 Example,
Let’s take a look how Amazon EC2 t1.micro Example Work so that we understand when to use them. By the end of reading this you should have a clear view of the behavior of the example so that you can understand its performance.
Amazon Web Services EC2 t1.micro instances consistently deliver a small amount of CPU resources and allow you to increase CPU capacity in short bursts when additional cycles are available. They are suitable for low throughput applications and web sites that periodically require additional computation cycles.
When not to use Amazon EC2 T1.Micro Instances
The t1.micro instance provides different levels of CPU resources at different times (up to 2 ECUs). By comparison, the m1.small instance type provides 1 ECU at all times. The following figures compare CPU usage. t1.micro instance vs a m1.small example for the same work load.
The figure above shows the profile for an application that is not suitable for a micro instance. The application requires constant data-crunching CPU resources for each request, resulting in a plateau of CPU usage that micro instances are not designed to handle.
The figure above shows another profile that is not suitable for micro instances. The spikes in CPU usage here are brief, but they are too frequent for the micro instance to be serviced.
The last one that is not suitable for a micro example. The spikes here are not very frequent, but the background level between spikes is too high to be serviced by the CPU micro instance.
When to Use T1.Micro Instances
The spikes in CPU usage here are brief and do away with even with very low background level CPUs. This is typically a low traffic website and/or well tuned one with moderate traffic where spikes can occur over a span of hours or days (eg cron backup scripts).
The t1.micro instance is designed to operate with its CPU usage at essentially only two levels: the normal low background level, and then at brief The peak level is much higher than the background level. Allows Amazon instances to operate up to 2 EC2 Compute Units (ECUs). It is greater than m1.small and similar to m1.medium. The above figure shows a CPU load profile suitable for a micro instance.
Your setup and web application will be different but for the most part your CPU profile should be within one of these 4 instances.
AMI Optimization for Amazon EC2 T1. micro instance
If you have decided to use a t1.micro instance, be sure to design the AMI to run on “600” MB of RAM or less, limiting the number of recurring processes that use CPU time (eg, cron jobs, daemons), if you’re running popular PHP applications like wordpress, drupal, joomla, etc., be sure to set up an opcode cache and use plugins/extensions that focus on moving processing from CPU to memory We do.
Examples of Successfully Using Amazon EC2 T1.Micro Instances
First a t1.Micro which runs a PHP web forum using AM AMI stripped down to use less than 50MB on boot. After this, I installed LEMP and RAM usage is still less than 150MB at boot.
Subsequently, a smaller website with about 100,000 page views per month, also hosted on t1.Micro. Like LEMP, I removed LAMP and custom tuned it because it was an existing server where the owner preferred Apache.