3 ms·

Opening the bio-assembly for 3J31 ate about 8 GB of my VRAM, and 32 of my system RAM, in ChimeraX. Which is actually less than I remember a few years ago. I won

Opening the bio-assembly for 3J31 ate about 8 GB of my VRAM, and 32 of my system RAM, in ChimeraX. Which is actually less than I remember a few years ago. I wonder if the render pipeline has changed a bit. That said, it's still very significant if you have 10-20 viruses attached to a cell, for instance. EDIT - that's also for atoms. Going to 3D maps is significantly more computationally intensive. A typical, sub-tomogram average, or annotation will be in MRC file format, which is horrendously slow with a box size > 1024 pixels or so.

dekhn 3y ago
THere's something wrong with your numbers. Opening 3j31 and turning on the complete assembly uses <<1GB extra system RAM and <1GB extra GPU RAM on my machine. I've worked with 3d maps and the same thing has been true for over 20 years: if you want to work with extremely large systems, you need an expensive graphics card (I was the first person to port Chimera to Linux some ~20 years ago, and we always compared the performance of my gaming cards to faster professional cards. for volumes like 3d maps, the largest volumes always were quite close to the largest graphics cards)