search

guillaumetousignant / NDG_cuda

MIT License
1 stars 0 forks source link

VTK compresses data on output, which ruins performance #8

Open guillaumetousignant opened 3 years ago

guillaumetousignant commented 3 years ago

Even when running with one process, when writing the VTK functions will use all 32 hardware threads of my machine at 100%, and use 127 GB out of the 128 GB of ram, and go back down afterwards. It will also take up the majority of the computation time. Compression should be disabled, or at the very least constrained to one process per program process.

guillaumetousignant commented 3 years ago

It does not seem to be compression. With multiple processes the time spent is only slightly lower, and the files are twice as big. With only one process the memory doesn't rocket up anymore, and the CPU is not pinned at all cores 100% anymore, but one core is at 100% and the others briefly spike at 100% together a few times. The time is slightly less.

guillaumetousignant commented 3 years ago

Turns out the "pinning the cpu at 100% and using 100% of RAM" is not happening even with compressioon anymore? What is happening?

guillaumetousignant commented 3 years ago

I was possibly using the compute-sanitizer? Or running a bigger mesh by accident maybe?