Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Design Implementation Decisions

In this section, the information gathered is translated into recommendations and requirements for the Sun Cluster Grid design. For each tier of the cluster grid, the impact of the information gathered is assessed.

Access Tier

At a minimum, the access tier has to be sized to support logins, telnet sessions, and job submissions (running simple binaries). Non-interactive jobs are executed through the queueing system by submitting a simple batch shell script which acts as a wrapper to the executable, and can be used to pass information to the queuing system, and to perform simple setup or cleanup tasks.

If users' own workstations are used to submit jobs, this represents a negligible load. However, if a single system is required to support hundreds of remote logins, it would be wise to ensure some dedicated resources.

Administrative access to the cluster grid is provided through the Sun Grid Engine and SunMC software. Both can be administered through a command line or GUI interface. Sun Grid Engine binaries and the GUI are supported on both Solaris™ and Linux operating environments. Binaries can also be obtained for other operating systems from the opensource site (see "Related Resources" on page 27).

The SunMC console, based on Java™, is supported on both SPARC systems running Solaris Operating Environment software (versions 8, 7 and 2.6) and Intel-based systems running Microsoft Windows 2000, NT 4.0 (with Service Pack 3 or 4), 98 and 95. For SPARC systems, the minimum system requirements for running the SunMC console are: Ultra 1 (or equivalent), 256 Mbyte RAM, 130 Mbyte Swap. For MS Windows Intel-compatible systems, the minimum requirements for running the SunMC Console are: 300 MHz Pentium, 256 Mbyte RAM, 35 Mbyte free disk space.

If web-based access is to be implemented, for example, using the Sun ONE portal server, the server must be sized appropriately for the expected load; this should take into account the sessions characteristics and headroom for future scalability.

Management Tier

The decisions to be made when designing the management tier depend on which services are to be provided, and the expectations for future scalability. For small cluster grids with a minimal service provision (DRM only), a single processor machine might suffice. As discussed in the previous article titled "Introduction to the Cluster Grid – Part 1", the master host functionality for Sun Grid Engine software is provided primarily through two daemons. Moving beyond a dedicated dual processor machine for the SGE master, therefore, results in limited performance enhancement. If a multiprocessor machine (more than two processors) is employed in the cluster grid as the SGE master, it would be appropriate for this machine to provide other services. For example, an eight-way server could act as an SGE master host, a Sun MC server, NFS and backup server as well as supporting computational tasks.

The load from the SunMC server is caused by normal management operations, including periodic data acquisition, alarm rule processing, alarm annuciation, alarm action execution, and processing of client requests. The generated load is proportional to the rate at which data is gathered, the amount of data gathered, the number of alarms detected and the number of user requests. The percentage of CPU resources consumed depends on the number and type of modules loaded on the system, the configuration of these modules, and the computational capacity of the host system. In general, even on low-end machines with a comprehensive suite of modules loaded and high management activity, the agent should never consume more than a fraction of the CPU resources. As with CPU consumption, the memory consumed by an agent depends on multiple factors.

The primary considerations are the number of modules loaded and the amount of information being monitored by these modules. Loading many management modules on an agent inevitably increases its footprint requirement. Similarly, agents managing hosts with large disk arrays or other highly scalable assets probably require more virtual memory, as the sheer volume of management information passing through them increases. In general, a base agent with the default set of modules loaded will be under 10 Mbyte in size, and under typical operation will only require 50–60% of this to be resident in physical memory.

NFS server sizing is a complex topic beyond the scope of this document. Obviously access to data files is a primary consideration, and the design is dictated by the application and type of work being done. The following list summarizes the other various elements of a cluster grid which might require a shared file system.

  • Sun Grid Engine software—By default, the SGE directory structure is shared across the cluster grid so that all execution, submit, and administration hosts access the same physical database. Non-default arrangements are discussed in "Sun Grid Engine Software Installation Considerations" on page 13.

  • User's Home Directories—As with nearly all DRMs, the input files and executables are arranged by the user, usually in their home directory or some working directory. When the job is submitted, by default the execution host must be able to access the files over a shared file system. Methods to minimize file-sharing network traffic are discussed in"File Sharing" on page 11.

  • Sun HPC ClusterTools™ 4.0 binaries—Two installation methods are available involving either a distributed install or a centralized install.

  • License Key server, application servers—Accessing application binaries from a shared location is beneficial because only one version of these files needs to be maintained for upgrades, bug fixes, and so forth.

  • Installation servers should have access to sufficient disk space to hold multiple Solaris images, software images, and flash archives, taking into account any RAID implementations.

Compute Tier

The decision of which hardware to implement in the compute tier is based primarily on maximizing performance/price. The overall hardware profile should closely match the user application profile. The hardware profiles pertaining to the throughput and highly parallel environments are at opposite extremes.

  • Throughput—Large numbers of thin nodes. Often the key requirement is to maximize the number of processors per unit volume rather than individual processor performance.

  • Highly Parallel—Depending on various attributes of the application, either a smaller number of large SMP nodes or a large number of thin nodes supported by a cluster runtime environment (CRE) will be appropriate.

A typical mixed load cluster grid for an academic site, for example, might consist of:

  • Distributed memory, network of workstations (NOW) interconnected with specialized high bandwidth low-latency interconnect and Ethernet.

  • A number of low- to mid-range independent servers for general tasks, interactive use, large memory serial jobs, and so on.

  • A large SMP system to support large OpenMP applications or other message passing applications, which benefit from ultra low-latency communications.

  • Workstations in student labs with standard fast Ethernet connections to be used at night, on weekends, and holidays for smaller one-CPU jobs.

Direct attached disk space on compute nodes that are part of a NOW cluster is usually used purely as scratch space and caching.

In a throughput environment, the compute tier should provide the resource to meet demand on some timescale. In FIGURE 1, the compute tier is sized to complete the submitted jobs on a daily basis. While the rate of job submission peaks during working hours, the available compute power enables jobs to be completed by the start of the next working day.

Figure 1FIGURE 1 Example of Daily Profile for Cluster Workload

Memory requirements and cache — Some applications benefit a great deal from large cache processors. In such cases, the aim is to maximize the proportion of the active data that is retained in cache, giving an order of magnitude lower access times than memory resident data.

Networking Hardware

Three interconnect types should be considered: serial, Ethernet and specialized low-latency interconnects.

Serial

A serial network allows the system administrator to gain console access to all the machines in a cluster. For large environments, this is a tremendous convenience, allowing almost complete control over all systems from a single remote location. The use of a terminal concentrator gives the administrator access to multiple console ports over the Ethernet network.

Ethernet

The network load in a cluster grid will originate from a number of activities:

  • MPI or PVM message passing communications at runtime for parallel applications in a distributed NOW

  • NFS traffic from various sources such as the following:

    • Cluster grid services accessing binaries, spool files, and so on

    • User directories being accessed at runtime for executables, input files, and so on

    • Sun Grid Engine communications

    • Data transfer from backups and installs

The load generated by this traffic (especially if no MPI traffic is involved) is handled satisfactorily with standard Ethernet or gigabit Ethernet. Techniques for reducing network load by minimizing file sharing are covered in the section, "File Sharing" on page 11". Ethernet capacity can be scaled through the use of multiple Ethernet cards. Shared file systems, for example, can be implemented through dedicated interfaces to separate NFS traffic from other network traffic.

Specialized Interconnects

Particular care should be made to avoid MPI traffic and other standard Ethernet traffic mixing if high communication intensity is a feature of the applications. One way to avoid this is to invest in a specialized low-latency interconnect for handling message passing communications. Alternatively, MPI applications may be run within large SMP machines where the interprocess communication takes place across the ultra-low latency specialized backplane.

Typical latencies for MPI communications between nodes over standard or gigabit Ethernet are over 100 microseconds. The maximum achievable bandwidth over gigabit Ethernet is around 700 Mbits per second. For many parallel applications, these latencies and bandwidths introduce a severe bottleneck to the calculations, and such specialized interconnects alleviate the bottleneck.

A Myrinet network is composed of interfaces, links, and switches. For Sun machines, the PCI interface is used with drivers tuned for Sun architecture, available from Myricom. Myricom supports a loadable protocol module (PM) for the Sun HPC ClusterTools 4.0 software. The PMs are used by Sun HPC ClusterTools software to carry the traffic between processes to exploit the low latency and high data rates of Myrinet. The Myrinet interconnect can reduce latencies by an order of magnitude, and can give higher aggregate bandwidths for compute clusters. Use of these specialized interconnects results in an added advantage of reduced load on the host processor as the message routing is processed in hardware on the Myrinet interface card.

Figure 2FIGURE 2 Three Types of Cluster Grid Interconnects

Storage

Full treatment of storage options is beyond the scope of this document, so a summary of the major options is outlined here.

If a large SMP server is part of the cluster grid compute tier, it might be appropriate for this server to provide the NFS service to the cluster grid. This ensures that the applications running on the large SMP have access to fast, direct storage, and provides some headroom for scaling the NFS service.

Choices of storage arrays depend very much on budget, availability, future scalability, and expected access patterns. Top-of-the-line disk arrays feature large caches, hardware RAID, and are compatible with SAN implementations. In some cases, the applications perform large volumes of random reads and writes and are better suited to a JBOD array (non-RAID storage implementations) with maximum spindle count.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020