Information Technology Reference
In-Depth Information
primary factor in determining the level of risk. Hard partitions are strongly
suggested, and perhaps required.
High-scale workloads need high-scale hardware. x86 systems may not scale
high enough, while SPARC systems are ideal. A high-scale operating system,
such as Oracle Solaris, will also play a key role.
■
Consolidated systems benefit from dynamic resource flexibility. The flexibil-
ity of Dynamic Domains will meet this need. A mid-range or high-end SPARC
system with 30 or more CPU cores is the ideal solution in this scenario. The
amount of RAM in the system should be slightly more than the sum of RAM
needed by all of the workloads.
■
As an ISP, you want to sell the service of web servers. The business model states a
desire to maximize the density of customers and minimize acquisition and main-
tenance costs. The customer service contract indicates an intent to achieve 99.9%
uptime, but includes a “best effort” clause regarding service uptime. Several con-
figurations will be offered, distinguished by CPU capacity and RAM (“cost units”
show the relative user cost per year):
Ve r y s m a l l : 0 . 1 C PU c o r e , 1 0 0 M B R A M , 1 G B d i s k : 1 × c o s t u n i t s
■
Small: 0.3 CPU core, 200 MB RAM, 2 GB disk: 2× cost units
■
Medium: 0.7 CPU core, 300 MB RAM, 4 GB disk: 4× cost units
■
Large: 1.5 CPU cores, 512 MB RAM, 8 GB disk: 20× cost units
■
Ve r y l a r g e : 3 . 5 C PU c o r e s , 2 G B R A M , 1 6 G B d i s k : 5 0 × c o s t u n i t s
■
These factors will help you choose:
The highest density of VEs per server requires the greatest efficiency—that
is, the least RAM and disk space per VE, and the least performance overhead
per VE. Containers provide the highest density of virtualization solutions
and are a good choice. With applications running, the Oracle Solaris kernel
will use hundreds of megabytes of RAM, but each VE will consume only doz-
ens of megabytes, plus the memory needed for the web server applications. A
two-socket, quad-core CPU, either x86 or SPARC, can easily handle 50 small
customers, or two very large customers.
■
Sparse-root Containers share OS binaries. Instead of potentially needing 50
copies of operating systems, which could use 200-300 GB of disk space, 50
Containers would need roughly 2.5 GB if you use ZFS clones. Customers will
■
Search WWH ::
Custom Search