Message boards :
Number crunching :
Anaconda Python 3 Environment v4.01 failures
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5
| Author | Message |
|---|---|
ServicEnginICSend message Joined: 24 Sep 10 Posts: 592 Credit: 11,972,186,510 RAC: 1,187 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
This week (february 22nd) I happened to catch one RAIMIS Python mt CPU task and an ADRIA ACEMD3 GPU task that ran concurrently. They ran at this 4 core CPU system. I have it configured to run CPU tasks at two CPU cores, leaving one more core for feeding GPU tasks, and another free core for smoothly attending OS needs. Ok, RAIMIS Python mt CPU task "kidnapped" for nearly one full day (85640 seconds) both CPU cores, preventing for executing apps from other projects. Anyway, It fits what could be expected for a multi thread CPU task. But to my surprise, it also slowed down notoriously the execution of the concurrent GPU task, making it to miss its usually awarded full bonus. GTX 1660 Ti GPU at this system takes usually 80 to 83 thousand seconds to process ADRIA ACEMD3 GPU tasks, while task that ran concurrently with the RAIMIS Python mt CPU task took more than 96 thousand seconds to process. |
Retvari ZoltanSend message Joined: 20 Jan 09 Posts: 2380 Credit: 16,897,957,044 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I've made that observation back in 2017 on my 4th generation CPUs. I'm avare that this haven't changed much throughout the years, so I basically don't run CPU tasks and GPU tasks simultaneously on the same PC, except when I need that much heat output in the winter. Lately I rather reanimate a few older GPUs, instead of crunching on CPUs. |
©2025 Universitat Pompeu Fabra