Thanks Warren for pymol 0.90. I started some serious ray-tracing jobs
last night, but stopped this morning when I saw your email about the new
faster version. With pymol 0.88, each image took 2:40h, with pymol 0.90
it takes 40 minutes. That's on a 2CPU PIII Xeon (linux). Fourfold!!
The windows box
Subject: Re: [PyMOL] pymol crashes with large pdb files
>
> Limited physical memory might indeed be the problem.
> When I ray-trace under WinXP, memory usage increases sharply (to about
> 500MB) and after a second or so, pymol crashes.
> When I ray-trace under linux, almost all phys
Limited physical memory might indeed be the problem.
When I ray-trace under WinXP, memory usage increases sharply (to about
500MB) and after a second or so, pymol crashes.
When I ray-trace under linux, almost all physical memory (1GB) is being
used. Barely 40MB available.
We should be getting new
> Now there is a twist to the story. We also run linux (redhat with 2.4.18
> kernel) on a 2 CPU 930MHz (1GB RAM, Nvidia GeForce2 GTS) PIII. Working
> speed is much slower but no crashes when ray-tracing from the exact same
> pml script.
> Can it be that linux makes better use of its physical memory
Sorry I didn't mention the operating system. It's WinXPpro. The
computers are a Xeon 2.8GHz (1GB RAM, Nvidia Quadro4 900XGL) and a P4
1.4GHz (768MB RAM, Nvidia GeForce2 GTS). Both run pymol 0.89.
Now there is a twist to the story. We also run linux (redhat with 2.4.18
kernel) on a 2 CPU 930MHz (1G
> Is there a limitation to the number of atoms or subunits pymol can handle?
> I reset max_triangles from 10^6 to 10^7. Didn't change a thing.
Exactly how much memory does your computer have? And what OS are you
running? I've definitely crashed PyMOL before on a Linux system when I
tried to do t
