On 15/04/2022 16:32, Qiuye Li wrote:
We recently centralized our high-end workstations and no longer have
easy access to their displays,
Someone drew the short straw there :-(
I found coot 0.9/wincoot 0.9 are a bit laggy on our less frequently
updated office computers,
You mean hardware updates? Yes, if you go back a gen or two, you will
notice this.
and the all-new coot 1 probably requires even more hardware resources?
It was my intention that Coot 1 be faster than 0.9.x in Basic mode -
Coot 1 is using the GPU in the way it was intended to be used - not
transferring the map line by line from the CPU to the GPU each frame.
So, with my machine, in the coot spin test, with a sampling rate of 2.5
and a radius of 99, Coot 0.9.8.1 spins at 5fps, and Coot 1 spins at
60fps for all render modes (limited by monitor sync).
Coot 1 has three render modes: Basic, Standard and Fancy. Basic mode
draws models with lines (like Coot 0.x does), Standard mode uses (only)
ambient, diffuse and specular lighting, Fancy mode adds brightness,
gamma, depth blur, SSAO and shadows.
Fancy mode in 4K fullscreen with a ribosome drops the frame rate to less
than 60 fps on my computer (RTX 2070 Super).
With this recent launch of coot 1, it is probably a good time to
kindly ask for hardware suggestions, like CPU, RAM, SSD, and dGPU.
With coot, I typically visualize a .mrc map using a radius of ~25 A
and work with real-space refinement/other simple manual adjustments.
Other than coot, I often have 1-2 active chimera/Phenix windows open,
a few SSH tunnels, and some web pages. [] Any suggestions are appreciated!
OK, so Coot 1 now takes more than 1 second to open in graphics mode on
my computers (SSD and m.2 NVMe PCIe 4). Coot 0.9.x was 0.35s. I haven't
tested it from a hard drive, but I can believe that Coot 1 would take
more than 10 seconds - that could be irritating. So m.2 NVMe 4 or 5 it is.
Since 2017 any function/algorithm that I've written that takes more than
1 second to complete is now written as multi-threaded (and I have
refactored several older algorithms to be multi-threaded also). So the
more of and faster the cores the better. I only have access to
workstation/Xeon processor at work - they are less speedy (and more
expensive (reliable though)). Although I haven't tried them myself I'd
recommend AMD Ryzen 5900X, 5950X or (the new) 5800X3D (the increased
size of the L3 cache could improve contouring and FFT speed).
Process size: I've seen coot get up to more than 20Gb - typically when
using map masking for cryo-EM maps. I have 32 Gb RAM on my main machine
and I haven't see Coot crash due to lack of memory. So I'd recommend at
least that especially if you have a multi-tabbed browser and other
graphics going also.
If you have a 4K monitor (if you don't have one, you should get one) and
want fullscreen 4K Fancy mode goodness (and to make pretty screenshots)
you'd want something better than my card, so the 3000 series, RTX 3070
or 3080. I don't follow AMD graphics cards sad to say. I intend to make
the interface to Blender increasingly powerful and easy to use - that
also will benefit from big memory and a fast graphics card.
So, get yourself a ballin gamer rig, and you'll have a ballin Coot
workstation :-)
The Best Coot Workstation today would be build around the AMD
Threadripper 3990X and Nvidia RTX 3090 Ti card and Dell UltraSharp
U4320Q monitor.
Paul.
########################################################################
To unsubscribe from the COOT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=COOT&A=1
This message was issued to members of www.jiscmail.ac.uk/COOT, a mailing list
hosted by www.jiscmail.ac.uk, terms & conditions are available at
https://www.jiscmail.ac.uk/policyandsecurity/