Specifications, costs, and trade-offs for upgrading and expanding the Matrix cluster.
From Scheraga, with Czarek, from 5/27/2014.
The bottom line IN THE FOLOWING BRIEF FORM is
A. Buy new head node
B. Buy new storage machine
C. Buy new computational nodes
D. Arrange an efficient back-up plan
Added by ChemIT:
E. Buy components for networking, power. And new rack.
STATUS, Option 1: Cost for A, C, and E: $46,500. Still need Storage and Backup costs.
Component |
Option 1 (most likely) |
Option 2 |
To consider, to do's, questions, notes and comments. |
---|---|---|---|
A. New head node |
Dedicated chassis |
One of four (a Quad), in one chassis. |
Consider Option 2 for cost savings (if any). |
B. New storage machine |
Synology-branded dedicated storage array. |
Home-brewed dedicated storage array, perhaps running OpenNAS software. |
Consider Option 2 for cost savings (if any). |
C. New computational node |
8 nodes (in 2 Quads), with higher computational processors. |
16 nodes (in 4 Quads), with standard computational processors. |
Consider Option 2 for increasing number of cores from 160 to 192, but with slower set of processors. See Czarek's note, from 4/14, below. |
D. Arrange an efficient back-up plan |
EZ-Backup |
(At current quantities of backed-up data, ChemIT cannot recommend an alternative.) |
On-going to do: Evaluate cost-effectiveness as volume grows. At current TB's of backup (including compression and versioning), costs are as were predicted (no surprises), and thus were at the time considered to be affordable and cost-effective compared to investing in own hardware and staffing. |
E. Components for networking, power. And new rack. |
Under $2,700. |
|
Specifics: |
4/14/14. Czarek: It looks like the slowest cpu E5-2620v2 2.1GHz has the best price performance ratio but anyway I would not buy the slowest cpu. Right now in Gdansk we are buying 10 servers and we decided to go for 10-core cpus E5-2670v2 2.5Ghz (20 cores per node). As in matrix in Gdansk we have only slow interconnect between nodes and some programs can run efficiently only on single node so more cores per node gives for such program advantage. Other programs both in Gdansk and on matrix just need the highest possible total performance and exchange very little data between nodes so than number of cores is not important. What about space restriction ? Is it better to buy smaller number of faster nodes?