<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi Artemis,
<div class=""><br class="">
</div>
<div class="">There are many things to consider, and you should consult with an IT expert for the details. But the big picture is as follows:</div>
<div class=""><br class="">
</div>
<div class="">- You need 4 GPUs if you want to use cryoSPARC Live in a way that it can keep up with data collection (it assigns two GPUs for motion correction, CTF estimation and particle picking, then one GPU for 2D classification, then the 4th GPU for 3D
reconstruction and refinement; if you have less then 4 GPUs, you need to stop one of these tasks to be able to start another, so it’s less automated).</div>
<div class=""><br class="">
</div>
<div class="">- The model of GPU you choose will pretty much dictate which case you need (some cases have enough room for only two of the latest GPUs). A common choice a couple years ago was 4 Nvidia RTX 2080 Ti. I don’t know about the latest models, but whatever
is the successor of this one should offer good performance for cryoEM data processing. In any case, you want the "blower" type cards, that exhaust the generated heat out of the case (as opposed to the regular type that exhausts heat around it inside the case,
which puts more strain on the case’s cooling system).</div>
<div class=""><br class="">
</div>
<div class="">- Don’t be cheap with RAM; 128 GB is an absolute minimum, and more will be helpful eventually (not all programs for cryoEM data analysis can use an SSD scratch disk).</div>
<div class=""><br class="">
</div>
<div class="">- Some job types in RELION are not GPU-accelerated (motion correction if you don’t use MotionCor2, bayesian polishing, CTF refinement), so more CPU cores is beneficial for these job types. If you face a compromise between less but faster CPU cores
and vice versa, it is almost certainly more beneficial to choose slightly slower CPU cores but more of them.</div>
<div class=""><br class="">
</div>
<div class="">- You absolutely need a dedicated SSD scratch disk. The OS is typically on an SSD in these workstations, so some people use their account’s home directory as a scratch space; but I would recommend against doing this! if not managed well, this
will eventually fill this disk, and you don’t want to run out of space on the disk housing the OS. The heavy read/write operations on the scratch space will also wear out the underlying disk faster, so again not a great idea for the disk housing the OS: in
case of disk failure, it’s a lot easier to change a separate, dedicated scratch disk than having to also reinstall the OS and all programs.</div>
<div class=""><br class="">
</div>
<div class="">- You absolutely need RAID6 for the workstation’s internal storage (or a 10 Gb/s link to the NAS, and the NAS setup in RAID6), this is the sweet spot between hardware fault tolerance and read/write performance. A slow storage space will be limiting
for the initial step of motion correction, where whole movies need to be read fast (and there are often too many movies to put them all on the scratch disk). I am using two systems, one with a 2-disk RAID1 and another one with a RAID6 (forgot how many disks
it has), and the difference in performance is very noticeable. On the RAID1 system, most of the time during a motion correction job is spent with the GPUs waiting for the disks; on the RAID6 system, the GPUs are all running at full capacity during the entire
job. And don’t be cheap with total usable storage space: having to move datasets in and out of the workstation too often because of limiting storage space is quickly annoying. I would say no less than 40 TB, but of course this depends a lot on how many datasets
you typically work on at any given time and how large each individual dataset can be.</div>
<div class=""><br class="">
</div>
<div class="">These guidelines are meant to optimize for performance, and a workstation of this type will likely be very noisy; but it should not be a big problem if you already planned a dedicated space for it.<br class="">
<div class=""><br class="webkit-block-placeholder">
</div>
<div class="">I hope this helps,</div>
<div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="Apple-interchange-newline">
Guillaume</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 5 Jan 2022, at 18:44, <a href="mailto:akosta@imm.cnrs.fr" class="">
akosta@imm.cnrs.fr</a> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Dear colleagues,<br class="">
I'm looking for advice on building a workstation for general compute tasks as well as cryo-EM data analysis (for example with Relion or cryoSPARC).<br class="">
The workstation will be placed next to a NAS storage device in our Data Center and few people will have access (less that 10). The informatics team will deal with installation and maintenance.<br class="">
Are there any minimal or/and optimal requirements, especially what would your GPU and RAM recommendation be?<br class="">
I am completely ignorant on this matter, so I will appreciate any advice!<br class="">
Best regards<br class="">
Artemis<br class="">
<br class="">
-- <br class="">
Artemis Kosta<br class="">
Service de microscopie<br class="">
FR3479 Institut de Microbiologie de la Méditerranée<br class="">
Aix Marseille Université<br class="">
31 chemin Joseph Aiguier, Bat N<br class="">
CS 70071 - 13402 Marseille cedex 09<br class="">
France<br class="">
<a href="mailto:akosta@imm.cnrs.fr" class="">akosta@imm.cnrs.fr</a><br class="">
0033 491 164055<br class="">
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.imm.cnrs.fr_microscopie_&d=DwIDaQ&c=-35OiAkTchMrZOngvJPOeA&r=L7-zyQ-04fFCMRqzLIOnx7H0exGZHwIQe_wMPuY600I&m=p2o4y9hYqgLOqKF0I9JDaDfJz-qh-YBAsE0yNa8KnAuQvopJQnP_drt_FwVVEslw&s=mMMscHYkoAtesPOcdF7Uewe7gPKjAmK9WQEdqKVp-Bw&e=
_______________________________________________<br class="">
3dem mailing list<br class="">
3dem@ncmir.ucsd.edu<br class="">
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<!DOCTYPE html>
<title>Page Title</title>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uu.se_om-2Duu_dataskydd-2Dpersonuppgifter_&d=DwQGaQ&c=-35OiAkTchMrZOngvJPOeA&r=L7-zyQ-04fFCMRqzLIOnx7H0exGZHwIQe_wMPuY600I&m=QZUuJijXm5Q6fNo2M_C9yWo4bFwNDZmAcd8eYR4oyCnXcRpTHJ8Gsww7JB_XFO9k&s=AbtB1bnJqmeYE6NO5LiYMQTuKNEkr33dnSlWsGrX9TE&e=">http://www.uu.se/om-uu/dataskydd-personuppgifter/</a>
<br>
<br>
E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uu.se_en_about-2Duu_data-2Dprotection-2Dpolicy&d=DwQGaQ&c=-35OiAkTchMrZOngvJPOeA&r=L7-zyQ-04fFCMRqzLIOnx7H0exGZHwIQe_wMPuY600I&m=QZUuJijXm5Q6fNo2M_C9yWo4bFwNDZmAcd8eYR4oyCnXcRpTHJ8Gsww7JB_XFO9k&s=HibWtvA-BgmJj3H0IAi6xENHTEGmQV6x5iFG8V4zAxs&e=">http://www.uu.se/en/about-uu/data-protection-policy</a>
</body>
</html>