Memory usage constantly growing with the number of perturbations. about protocaller HOT 6 CLOSED

Hi, could you reproduce this on some simpler ligands because waiting for all the ligands to parametrise will take quite a long time? Alternatively, you could perhaps upload all of the parameter files instead. I tried reproducing this on a T4-lysozyme system bound to chains of hydrocarbons and I don't seem to have any memory issues. My garbage collection seems to be releasing memory just fine after each iteration.

from protocaller.

Ligands.zip
Hi @msuruzhon , these are the parameter files I used. Hope it helps!

from protocaller.

Thanks @kexul, I profiled these overnight and they ran just fine on my 8 GB machine. If you look at the attached graph you can see that the memory only goes up to about 5 GB at most, which is to be expected for this large system. The steady increase over time is most likely due to storing the morph objects – this is relatively cheap and needed because alignment and morphing can be slow in some cases. Do you think that your issues might be related to some other programs running? You still need most of your memory to be free in order to run these, or alternatively you could increase your swap file size.

from protocaller.

Hi @msuruzhon , thanks for your work! Your suggestion remind me that I did not have swap file in my system. I'll try increase it.

By the way, I used these code to reproduce the benchmark and got a pearson R of 0.65 in CDK2. Thanks for your great work!

from protocaller.

Thank you for your kind words @kexul! I am always happy to hear ProtoCaller produces structures that perform well on benchmark calculations, especially since it seems that this performance is comparable to commercial packages :)

from protocaller.

Yeah, that's amazing @msuruzhon !!

from protocaller.