You may be considering a farm with a certain number of cores and job queues to satisfy your current processing requirements. We strongly recommend you consider your future needs before setting up even a small farm, so that you can continue to use the hardware you choose now as part of the larger farm you may need tomorrow.
Click on the quick recommendation section title ("Processors, "Networking", etc.) for detailed discussion on that topic:
Most major vendors (IBM, HP, Dell etc.) offer rack servers designed for the Xeon E5-2600 V4 series
The Dell PowerEdge R730 is a good example of a 2U server that supports two Xeon E5-2600 V4 series chips and up to sixteen 2.5" SAS drives.
Sample Configuration Notes:
The Intel E5-26xx V4 processors carry our top recommendation for use with GridLink. In general, the higher the core clock speed the better each core will perform. Sixteen 3.4 GHz cores, for example, will outperform sixteen 2.6 GHz cores. 3.4 GHz clock speeds, however, are only available on 8 core processors while 2.6 GHz processors are available with 16 cores. So you would needtwice as many 3.4 Ghz processors to get the same number of cores. As a result, other factors such as server and operating system costs, licensing fees, and your datacenter density and power consumption requirements should be considered along with your speed requirements to determine the optimal processors for your environment.
Our top recommendations are as follows:
We are disappointed by the performance of 4-processor and 8-processor servers for high performance computing so at this time we will not recommend their use in a GridLink farm.
Connect up all the servers in your GridLink farm on the same subnet using at least 1 Gbps networking. This applies even if the rest of your datacenter is using a 100Mbps network. InfiniBand or 10G Ethernet is preferred but not required and will have the most benefit on the Master servers.
[January 28th, 2016] Please refer to the update on SMB advisory for Windows Server 2012 R2 at the link below:
We do not recommend virtualizing GridLink servers as the hypervisor layer reduces the performance of the hardware. We do, however, support virtual machines in those environments where there is no direct access to “bare metal” hardware, such as public clouds.
This support is conditional on meeting the following minimum requirements:
You will need at least 4GB of memory per processor core.
Please note that each Windows version has its own memory limit. For details, please review Microsoft KB article "Memory Limits for Windows Releases".
For new installations we recommend Windows Server 2016 Standard or Datacenter. Windows Server 2012 R2 Standard, Windows Server 2012 Standard and Windows Server 2008 R2 Enterprise are also supported. We no longer recommend Windows Server 2008 R2 Standard as it is limited to 32 GB of memory per machine. With modern 24+ core servers, this is not enough to meet our minimum requirement of 4 GB of memory per core. Window Server 2008 R2 Enterprise supports 2 TB of ram per machine and 2012 (R2) Standard supports up to 4 TB.
Note that we can only support versions of the Windows operating system as long as its official support from Microsoft is still valid. Please refer to this page to check on the Microsoft support lifecycle for each OS:
GridLink servers require access to large amounts of high speed storage. This storage is temporary - it is used during the calculations, but no data is stored there permanently. We recommend the larger of either:
Minimum disk performance should be the equivalent to 3 x 15k drives in Raid 0, with 4 x 15k drives in Raid 0 being recommended when using servers with more than 24 cores. For very high core density servers (greater than 30 cores), we recommend a minimum of 3 x SSD drives in raid 0. If a disk failure occurs on a helper server, the work is automatically redistributed to other nodes, so disk redundancy on helper servers is optional. On master servers, however, it is recommended to provision disks in Raid 10 so that disk failure does not cause running jobs to fail. You may also provide separate drives (RAID 1) for the O/S on both Master and Helpers servers although this is not a GridLink requirement or a GGY recommendation. You can save money and drive bays by introducing an O/S partition of say 100GB on the main RAID array.
We recommend that this storage be provided via local disks. For master servers only, you can alternately provision the drives via a direct fiber connection to a suitable SAN. The SAN, however, needs to be able to sustain performance equivalent to the local disk configurations noted above. Helper servers should not be provisioned with disks residing on a SAN. Given the temporary nature of the data stored on the helper servers, and the automatic recovery mechanisms, there is no advantage associated with the added expense of SAN based disks. In addition, we have seen situations where the combined throughput of a large number of helper servers has caused congestion and performance problems even on enterprise grade SAN devices.
Important - Hard Disk Performance
These types of software will cause severe instability and performance issues.
You can now choose how many cores you want in a server farm and how many Queues you want on that farm. Note that each Queue requires a separate server. The number of Queues should correspond to how you wish to use the farm. For example, you may wish to set up separate Queues for Pricing, Testing and Valuation. You can buy GridLink Core licenses ($1000 per core) and GridLink Queue licenses ($4000 per Queue) to support the configuration you require. Special pricing is available for Large Farms (256 cores or greater).
A server with a GridLink Queue license is a Master server, and without it, it's a Helper server. In most cases the requirements for master and helpers servers are the same except that we recommend redundant disk configurations on the masters but redundancy is optional on the helpers. If mixing different server configurations, the GridLink queue licenses should always be attached to the servers with the fastest processors and best disk subsystems in the farm.
We strongly recommend that the datasets you run should be stored on a network share with fast and reliable connection between the server hosting this share and the Master servers in your farm. The GridLink service will automatically copy the Dataset from its current location to the drive of the Master server before the job starts, and copy it back once the job is complete. This is a change from our earlier recommendation to store the datasets on the drive of the Master server. The reason for this change is that the end user may be opening datasets located on the Master Server’s drives and running jobs or performing other disk intensive tasks locally on his/her desktop or front-end/EnterpriseLink server before or after the GridLink run This may impose an additional load on the GridLink server's drive system that can cause a significant deterioration in performance or in some cases instability on both sides: the GridLink runs as well as in the users’ interactive AXIS sessions.
Some Blade servers offer excellent performance and flexible storage options, but many Blade servers provide very limited disk capacity, speed, and do not support the fast processors. As a result, you need to be careful that the recommended storage, memory and processors are available in the Blade chassis that you are considering. Some 1U rack servers are also limited to two 3.5" drives or four 2.5" drives. We recommend 2U rack servers for their storage abilities. If you are using Blade or other small servers you may get the disk speed you need by using SSD drives or Fusion IO cards.
If you implement our current recommendations for storing the datasets outside of the GridLink farm you no longer have any data residing on the GridLink master’s or helper’s drives that needs backing up. Taking a snapshot or image of the server to be able to recover the operating system and installed executable files should be quite sufficient. Even this may not be needed as re-installing GridLink is usually a very quick process. You should consider backing up the farm profile after every configuration change for faster recovery. See this page for more information: https://ggy.com/gridlink/farm_recovery.htm
For the partitions outside of the GridLink farm that house the datasets and other user data files we now provide intelligent, safe and fully automated backup functionality built into the AXIS EnterpriseLink module. For more information please contact GGY System support.
Do not perform backups using third party tools on GridLink Master or Helper servers while AXIS is running under any circumstances. The backup you perform may lock files that AXIS needs and produce errors and the backup will also be unusable since it may be made while the dataset is changing.
that still house the datasets on the local drives of the Masters we have built
an intelligent backup facility into GridLink itself. It allows you to schedule
backups like other backup software but it will not attempt to back up a dataset
that is running - it will wait for a suitable time. The backup it produces is
simply a zip file for each Dataset or Database located in a safe place for you
to backup later using your normal backup software.
We recommend that you set up one or more AXIS EnterpriseLink front end servers to support the interactive clients who are using your farm, and also for those who do not require farm access. EnterpriseLink is included in your AXIS license.
For more information please visit AXIS EnterpriseLink web site or contact GGY.