Difference between revisions of "Suggestions for suitable hardware to run a Grid SE"
m |
|||
| Line 5: | Line 5: | ||
=Headnode with diskservers vs distributed model= | =Headnode with diskservers vs distributed model= | ||
| + | A single storage node is unlikely to be used on its own as the entire storage system. I tis likely to be used as a either one of many disk servers in a system with(out) multi it own set of gatweways (ie dCache/DPM). It may also be used within a single distributed file system which on top has a few gateways for external access. (Lustre/GPFS?HPDFS/Ceph etc.) This may lead to varying requirements on the amount a capability. | ||
=Head node requirement discussion= | =Head node requirement discussion= | ||
| Line 13: | Line 14: | ||
=Disk server requirement discussion = | =Disk server requirement discussion = | ||
| + | The number of concurrent connections, the length of time the se connections are expected to be open. And the middleware component may lead to differing amounts of required CPU and Memory per disk server. | ||
== Memory== | == Memory== | ||
| Line 23: | Line 25: | ||
== Network capabilities.== | == Network capabilities.== | ||
| − | Limiting factor | + | Local network configuration ,may effect number and size of network capacity of your storage nodes. |
| + | Limiting factor maybe LAN access by worker nodes needed by of your storage. | ||
Assuming that your WNs have 1Gbps NICs, then the ~ absolute maximum your disk server (DS) requires is (<#_of_WNs>/<#_of_DSs>) Gbps. IE to match the disk server bandwidth to possible client bandwidth needs... | Assuming that your WNs have 1Gbps NICs, then the ~ absolute maximum your disk server (DS) requires is (<#_of_WNs>/<#_of_DSs>) Gbps. IE to match the disk server bandwidth to possible client bandwidth needs... | ||
| Line 36: | Line 39: | ||
A site might also want to take into account the capabilities of their backbone connection WNs to their disk servers. | A site might also want to take into account the capabilities of their backbone connection WNs to their disk servers. | ||
- | - | ||
| − | {{KeyDocs|responsible=Brian Davies|reviewdate= | + | {{KeyDocs|responsible=Brian Davies|reviewdate=2017-02-16|accuratedate=2017-02-16|percentage=15}} |
Revision as of 09:43, 16 February 2017
This page list ssuggestions for hardware to run a grid SE. You may also want to look at:
https://www.gridpp.ac.uk/wiki/Performance_and_Tuning
Contents
Headnode with diskservers vs distributed model
A single storage node is unlikely to be used on its own as the entire storage system. I tis likely to be used as a either one of many disk servers in a system with(out) multi it own set of gatweways (ie dCache/DPM). It may also be used within a single distributed file system which on top has a few gateways for external access. (Lustre/GPFS?HPDFS/Ceph etc.) This may lead to varying requirements on the amount a capability.
Head node requirement discussion
Memory CPU Required Services Database Issues
Disk server requirement discussion
The number of concurrent connections, the length of time the se connections are expected to be open. And the middleware component may lead to differing amounts of required CPU and Memory per disk server.
Memory
CPU
Capacity of Server/Disk
Rackspace and power connection are a consideration.
Network capability is a factor.
Network capabilities.
Local network configuration ,may effect number and size of network capacity of your storage nodes. Limiting factor maybe LAN access by worker nodes needed by of your storage.
Assuming that your WNs have 1Gbps NICs, then the ~ absolute maximum your disk server (DS) requires is (<#_of_WNs>/<#_of_DSs>) Gbps. IE to match the disk server bandwidth to possible client bandwidth needs...
A correction to this is to incorporate the fact that your DSs are of different size. And so rather dividing <#_of_WNs> by <#_of_DSs>. Then take the relative proportion that the DS is expected to be of your whole SE. Ie rate= (<#_of_WNs>*<Size_of_newDS>/<Total_size_of_SE>) Gbps.
This calculation assumes you are going to max out the network connectivity of your WNs. If you want a better estimation. You can calculate the network capacity needed by your WNs to be ( as an example) ~25Mbps per job slot. Therefore if you had 500 job slots, you would require that your storage would have 12.5Gbps of network capcity. If you only had 5 disk servers then each would require 2.5Gbps of network capacity.
The addidtion concept would then say that this 12.5Gbps needs to be split over my Storage, I current have 100TB of storage, I am buying 150TB more in X number of servers therefore the new servers need to have 12.5* 150/(100+150)/X Gbps. ie 7.5/X Gbps
A site might also want to take into account the capabilities of their backbone connection WNs to their disk servers. -
This page is a Key Document, and is the responsibility of Brian Davies. It was last reviewed on 2017-02-16 when it was considered to be 15% complete. It was last judged to be accurate on 2017-02-16.
