Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Bump default instance type parameters #6

Merged
merged 1 commit into from

8 participants

@gholms
Owner

The default parameters for instance types are far too small for modern
hardware and software. This commit bumps them to the following values:

  • m1.small: 1 CPU, 5 GB disk, 512 MB RAM
  • c1.medium: 2 CPUs, 10 GB disk, 512 MB RAM
  • m1.large: 2 CPUs, 15 GB disk, 1024 MB RAM
  • m1.xlarge: 2 CPUs, 20 GB disk, 2048 MB RAM
  • c1.xlarge: 4 CPUs, 20 GB disk, 4096 MB RAM
@gholms gholms Bump default instance type parameters
The default parameters for instance types are far too small for modern
hardware and software.  This commit bumps them to the following values:

 - m1.small:  1 CPU,   5 GB disk,  512 MB RAM
 - c1.medium: 2 CPUs, 10 GB disk,  512 MB RAM
 - m1.large:  2 CPUs, 15 GB disk, 1024 MB RAM
 - m1.xlarge: 2 CPUs, 20 GB disk, 2048 MB RAM
 - c1.xlarge: 4 CPUs, 20 GB disk, 4096 MB RAM
ca89b13
@gholms
Owner

These instance types are still smaller than EC2's, but this is mainly due to the fact that EC2's smallest instance type has 0 instance storage, which Eucalyptus doesn't support, and the next smallest instance type has 160 GB of instance storage, which I suspect is larger than most users are going to want as a minimum.

@a13m

I certainly agree with bumping the RAM in the smallest types to 512, as well as bumping the disk up to 5 GB. I'm not sure about the rationale of a couple of the choices, though, such as the 15 GB disk size for m1.large. I don't want to hold up a useful usability change by splitting hairs, but could you elaborate on these choices a little bit? Why not have higher RAM limits ? In general, I think RAM : CPU core ratios are a bit higher these days than what these numbers allow.

Also, FWIW, this issue was raised here: https://eucalyptus.atlassian.net/browse/EUCA-595

@JMoLo
@rudygodoy

Here's a 2009's RightScale report that among other interesting data shows that most EC2 customers are migrating from small instances to larger instances for scaling, as opposed to launching more instances.

http://blog.rightscale.com/2009/10/05/amazon-usage-estimates/

Realistically most instances are setup to run applications, particularly web applications. I don't see a web app running in a 2GB disk with 512RAM instance.

@a13m

JMoLo, there's a bit of a problem in that a hobbyist with an old workstation will want a very different set of parameters from someone with a modern enterprise-class server. It might seem easy to argue for what the enterprise user wants, except that if you aim too high, the out-of-box experience for the hobbyist will be an inability to launch instances until the properties are tuned. Proposing a change from 128MB to 512MB is a no-brainer on the low-end, because many distros simply won't boot with less than 512 MB of RAM. Once you get beyond that obvious threshold, though, there's no simple answer. You are welcome to start a poll, though. :-)

@viglesiasce
Owner

I think these defaults presented by gholms are quite sane and strike a good balance between the hobbyist and enterprise.

@a13m

After talking to Dan, I've sent a note to Eucalyptus Product Management to get their opinion. Will push this through if they think the numbers make sense.

@gholms
Owner

I arrived at these numbers after consulting with @hspencer77 since he has experience with so many Eucalyptus clouds. I'm not particularly picky about the specific numbers; I simply care about bumping them to values that are reasonable for this day and age.

@grze
Owner

Merging it.

@IForOneWelcomeOurNewRobotOverlords IForOneWelcomeOurNewRobotOverlords merged commit ca89b13 into eucalyptus:testing
@sangmin
Owner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Oct 8, 2012
  1. @gholms

    Bump default instance type parameters

    gholms authored
    The default parameters for instance types are far too small for modern
    hardware and software.  This commit bumps them to the following values:
    
     - m1.small:  1 CPU,   5 GB disk,  512 MB RAM
     - c1.medium: 2 CPUs, 10 GB disk,  512 MB RAM
     - m1.large:  2 CPUs, 15 GB disk, 1024 MB RAM
     - m1.xlarge: 2 CPUs, 20 GB disk, 2048 MB RAM
     - c1.xlarge: 4 CPUs, 20 GB disk, 4096 MB RAM
This page is out of date. Refresh to see the latest.
View
10 clc/modules/cluster-manager/src/main/java/com/eucalyptus/util/MetadataStateBootstrapper.java
@@ -99,11 +99,11 @@ private static void ensureVmTypesExist( ) {
EntityWrapper<VmType> db = EntityWrapper.get( VmType.class );
try {
if ( db.query( new VmType( ) ).size( ) == 0 ) { //TODO: make defaults configurable?
- db.add( new VmType( "m1.small", 1, 2, 128 ) );
- db.add( new VmType( "c1.medium", 1, 5, 256 ) );
- db.add( new VmType( "m1.large", 2, 10, 512 ) );
- db.add( new VmType( "m1.xlarge", 2, 20, 1024 ) );
- db.add( new VmType( "c1.xlarge", 4, 20, 2048 ) );
+ db.add( new VmType( "m1.small", 1, 5, 512 ) );
+ db.add( new VmType( "c1.medium", 2, 10, 512 ) );
+ db.add( new VmType( "m1.large", 2, 15, 1024 ) );
+ db.add( new VmType( "m1.xlarge", 2, 20, 2048 ) );
+ db.add( new VmType( "c1.xlarge", 4, 20, 4096 ) );
}
db.commit( );
} catch ( Exception e ) {
View
10 clc/modules/cluster-manager/src/main/java/com/eucalyptus/vm/VmTypes.java
@@ -201,11 +201,11 @@ private synchronized void update( ) {
}
if ( vmTypeList.isEmpty( ) ) {
- db.add( new VmType( "m1.small", 1, 2, 128 ) );
- db.add( new VmType( "c1.medium", 2, 5, 128 ) );
- db.add( new VmType( "m1.large", 2, 10, 512 ) );
- db.add( new VmType( "m1.xlarge", 2, 10, 1024 ) );
- db.add( new VmType( "c1.xlarge", 4, 10, 2048 ) );
+ db.add( new VmType( "m1.small", 1, 5, 512 ) );
+ db.add( new VmType( "c1.medium", 2, 10, 512 ) );
+ db.add( new VmType( "m1.large", 2, 15, 1024 ) );
+ db.add( new VmType( "m1.xlarge", 2, 20, 2048 ) );
+ db.add( new VmType( "c1.xlarge", 4, 20, 4096 ) );
}
db.commit( );
} catch ( Exception e ) {
Something went wrong with that request. Please try again.