-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorial Compute Time #10
Comments
I just checked and the runs that I did while writing the tutorial do a time step in about 15 seconds, so the 200 steps take 50 min. That is on a Core i5-2400 @ 3.1GHz from 2011. So your run time seems to suffer indeed from some bottleneck. The most obvious guess for the bottleneck is probably disk I/O. If you use a network-mounted file system with low bandwidth/latency for the "scratchdir", then the MOLCAS performance will probably suffer quite a lot. In my case, I used the local hard drive of my computer as the scratchdir. This works quite well because it is not affected by other users, unlike a large global cluster file system that is busy with dozens (or more) of other jobs. If that does not help, then you can send me a zip containing all your output files (SHARC input, output.*, content of the QM/ directory, content of scratchdir). Email probably works best for this. |
OK, 50 minutes is a lot closer to what I was expecting. I will have to work with my system administrators to see if we can get to the bottom of this. I noticed that only ~10-20% of the CPU was actually being utilized at any given time, so I am going to look into that first. I will get back to you later. Thanks again |
I believe I got to the bottom of this.
Thanks for the guidance! Closing issue |
I apologize if GitHub Issue tracking is not the appropriate location for this type of dialogue. If there is a forum or group page where such questions should be posted instead, please let me know.
Now that I have been able to complete the tutorial, I am curious about the expected computer time required for each trajectory. I had originally anticipated that the calculation for a single trajectory from the tutorial would be quite fast for several reasons: the relatively short trajectory length (100 fs with 0.5 fs timesteps = total of 200 steps), the low level of theory (CASSCF), small basis set (cc-pVDZ), small molecule (CH2NH2), etc. Instead, each trajectory required approximately 12 hours to complete on a single CPU, Intel(R) Xeon(R) CPU E5-2695 v4 @ 2.10GHz. Is this a typical run time for a single trajectory from the tutorial? If not, what might be the bottleneck? I would assume it is the QM calculations with OpenMOLCAS, in which case I am not sure how to improve performance.
The text was updated successfully, but these errors were encountered: