Ideas: Expand computational capabilities (power and/ or number of computers), increase efficiency of code, streamline workflows, etc.
Purpose of page
Write down concerns, ideas, and efforts as understood by Chemistry IT so research group members can review and correct.
Status
10/5/17: Oliver met with Mahdi <mh2356> and Kushal <ks2285>. Action steps to have Peng review and refine:
(1) Group: Decide if worth having (select?) Matlab code reviewed by experts at CAC, focused primarily to increase efficiency. Secondary outcomes include:
- May result in the ability to run older code on current version of Matlab, expanding where code could run on non-group computers.
- May result in clarifying computational bottlenecks so the best fitted computational hardware is purchased. What does one prioritize when faced with choice to invest in: better processors, number of processors, number of cores per processors, bus speeds, SSD drives, and/ or RAM?
- May result in a confirmation whether or not problem lends itself to parallelization. If so, can increase efficiency with the right hardware and expands the locations to efficiently run the code (RedCloud, etc.).
(2) Oliver: Have group test their code on test server in 248, initially by-passing using the network to get the data to the server.
- Time comparisons of both single runs and simultaneous runs. Does the server reduce computational time for a single job, as compared to current workstations? To what degree does the server's performance drop as more jobs are added? Again, compare to current workstations.
(3) Oliver: Optimize getting data to test server in 248 via the network.
Other thoughs from Oliver:
- Confirm if any campus computing is a good fit for the group: CISER, RedCloud (likely only if code can be and is parallelized), David Botsh's cluster(?), others?
- Group may benefit from optimizing workflow at various workstations.