| Anonymous | Login | Signup for a new account | 06-10-2026 07:17 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0004872 | [Resin] | minor | always | 11-23-11 23:15 | 06-11-12 15:05 | ||||
| Reporter | rickHigh | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | no change required | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | Product Version | ||||||
| Product Build | |||||||||
| Summary | 0004872: Resin too big to run in Amazon AMI micro, need Resin minimal mode | ||||||||
| Description |
Resin assumes a larger memory space and more CPU muscle that Amazon micro provides. It often seems like when doing deploys where Resin must unpack and compile that it is taking long time. The issue is micro might be too small and Resin needs a mode where it is tuned to run in an micro instance. Micro Instance 613 MB memory 1 EC2 Compute Units (up to two but only for short bursts) EBS storage only I/O Performance: Low API name: t1.micro 1 EC2 compute unit is essentially a 2007 Xeon processor. ------ When I lost www-user it was after the micro instance resin was deployed on crashed. This took a while to reset things properly (might of been faster to just delete the instance and start over). Assuming the OS is going to use memory and there is only 613 MB, this does not leave much for Resin. Resin should be configured to work in this constrained environment. There needs to be a minimal mode. ----------- From Amazon.... Q: What is a ?EC2 Compute Unit? and why did you introduce it? Transitioning to a utility computing model fundamentally changes how developers have been trained to think about CPU resources. Instead of purchasing or leasing a particular processor to use for several months or years, you are renting capacity by the hour. Because Amazon EC2 is built on commodity hardware, over time there may be several different types of physical hardware underlying EC2 instances. Our goal is to provide a consistent amount of CPU capacity no matter what the actual underlying hardware. Amazon EC2 uses a variety of measures to provide each instance with a consistent and predictable amount of CPU capacity. In order to make it easy for developers to compare CPU capacity between different instance types, we have defined an Amazon EC2 Compute Unit. The amount of CPU that is allocated to a particular instance is expressed in terms of these EC2 Compute Units. We use several benchmarks and tests to manage the consistency and predictability of the performance from an EC2 Compute Unit. One EC2 Compute Unit provides the equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor. This is also the equivalent to an early-2006 1.7 GHz Xeon processor referenced in our original documentation. Over time, we may add or substitute measures that go into the definition of an EC2 Compute Unit, if we find metrics that will give you a clearer picture of compute capacity. |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0005820) ferg 06-11-12 15:05 |
Use -Dcaucho.smallmem=true |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 11-23-11 23:15 | rickHigh | New Issue | |
| 06-11-12 15:05 | ferg | Note Added: 0005820 | |
| 06-11-12 15:05 | ferg | Assigned To | => ferg |
| 06-11-12 15:05 | ferg | Status | new => closed |
| 06-11-12 15:05 | ferg | Resolution | open => no change required |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |  |
