That makes sense, and 4 cpus seems to be reasonable, so if you are using Amazon EC2 for instance, you would be prohibited from using only the largest of instances for standard, but others should be ok, correct? Up to 4 virtual cores should be fine with windows or linux?
Standard Instances Instances of this family are well suited for most applications. Small Instance (Default) 1.7 GB of memory, 1 EC2 Compute Unit (1 virtual core with 1 EC2 Compute Unit), 160 GB of local instance storage, 32-bit platform Large Instance 7.5 GB of memory, 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform Extra Large Instance 15 GB of memory, 8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform Micro Instances Instances of this family provide a small amount of consistent CPU resources and allow you to burst CPU capacity when additional cycles are available. They are well suited for lower throughput applications and web sites that consume significant compute cycles periodically. Micro Instance 613 MB of memory, up to 2 ECUs (for short periodic bursts), EBS storage only, 32-bit or 64-bit platform High-Memory Instances Instances of this family offer large memory sizes for high throughput applications, including database and memory caching applications. High-Memory Extra Large Instance 17.1 GB memory, 6.5 ECU (2 virtual cores with 3.25 EC2 Compute Units each), 420 GB of local instance storage, 64-bit platform High-Memory Double Extra Large Instance 34.2 GB of memory, 13 EC2 Compute Units (4 virtual cores with 3.25 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform High-Memory Quadruple Extra Large Instance 68.4 GB of memory, 26 EC2 Compute Units (8 virtual cores with 3.25 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform High-CPU Instances Instances of this family have proportionally more CPU resources than memory (RAM) and are well suited for compute-intensive applications. High-CPU Medium Instance 1.7 GB of memory, 5 EC2 Compute Units (2 virtual cores with 2.5 EC2 Compute Units each), 350 GB of local instance storage, 32-bit platform High-CPU Extra Large Instance 7 GB of memory, 20 EC2 Compute Units (8 virtual cores with 2.5 EC2Compute Units each), 1690 GB of local instance storage, 64-bit platform -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 15520 Coutelenc Rd Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 rgar...@bighead.net - rgar...@eventpix.com http://bighead.net/ - http://eventpix.com/ On Oct 13, 2010, at 2:45 PM, Robert Shubert wrote: > Robert, > > That is correct, the Standard Edition will simply not run at all if you try > to launch it on server with more than 4 physical cores (8 threads with HT). > > The technology to count cpus, cores, threads and support affinity is a mess. > Microsoft does the best job at sorting it all out, but only in certain > circumstances. OS X is horrible, and really doesn't have affinity control > (it's more of a suggestion). Linux is someplace in the middle, but all 3 > platforms would require unique code to support some sort of affinity. > > I've opted to simply use all of the available processing power on any given > machine, and limit the licenses to what "size" of machine they can be used > on. It's also notable that the OS thread managers are getting very good at > their jobs, and doing any sort of thread management internal to an > application is usually a less then optimal solution. > > Since most server OSes now support virtualization, if someone has a monster > 12-core/24-thread server that they need to run the Standard Edition on, then > a virtual machine with 4 virtual CPUs is their answer. So I don't really > consider this a practical limitation, simply one of scale. > > You may be interested to know that www.witango.com is being served with the > latest build of Server 6 running on a Hyper-V virtual server. > > Robert > > > -----Original Message----- > From: Robert Garcia [mailto:wita...@bighead.net] > Sent: Wednesday, October 13, 2010 5:26 PM > To: Witango-Talk@witango.com > Subject: Re: Witango-Talk: Standard and Advanced > > I am a bit confused, if you can't run on a server with more than 4 cores, and > then you say affinity is removed. Does that mean that if more than 4 cores, > it just won't run? But if it runs affinity is removed? > > 4 cores seems pretty reasonable to me, by the way. > > -- > > Robert Garcia > President - BigHead Technology > VP Application Development - eventpix.com > 15520 Coutelenc Rd > Magalia, Ca 95954 > ph: 530.645.4040 x222 fax: 530.645.4040 > rgar...@bighead.net - rgar...@eventpix.com > http://bighead.net/ - http://eventpix.com/ > > On Oct 13, 2010, at 7:09 AM, Robert Shubert wrote: > >> Wayne, >> >> We just updated this section of the website yesterday: >> >> https://www.witango.com/products/licensing >> >> As it shows, there are 2 restrictions on the Standard Edition: >> >> - You can only run it on a server with 4 or fewer CPU cores. >> - You can only run a single instance on each server. >> >> The Advanced Edition removes these two limitations. >> >> Also, future versions of the v6 product line will add some features to the >> Advanced server only. These features will be mostly geared towards better >> server pooling support for high traffic websites. >> >> The Standard Edition is being sold for use on workstations, entry-level >> servers, older hardware, and virtual servers. >> >> In all cases, the Witango server will use all addressable CPUs. Affinity has >> been removed from the product. >> >> Robert >> >> -----Original Message----- >> From: Wayne Irvine [mailto:wa...@byteserve.com.au] >> Sent: Tuesday, October 12, 2010 11:39 PM >> To: Witango-Talk@witango.com >> Subject: Witango-Talk: Standard and Advanced >> >> I'm guessing this has been covered before but in my cursory glance over the >> archives I didn't see it. >> >> What is the difference between the Standard and Advanced Servers in version >> 6? >> >> Wayne Irvine >> >> >> >> ---------------------------------------- >> >> To unsubscribe from this list, please send an email to lists...@witango.com >> with "unsubscribe witango-talk" in the body. >> >> >> >> ---------------------------------------- >> >> To unsubscribe from this list, please send an email to lists...@witango.com >> with "unsubscribe witango-talk" in the body. >> > > > > ---------------------------------------- > > To unsubscribe from this list, please send an email to lists...@witango.com > with "unsubscribe witango-talk" in the body. > > > > ---------------------------------------- > > To unsubscribe from this list, please send an email to lists...@witango.com > with "unsubscribe witango-talk" in the body. > ---------------------------------------- To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
