DPAD Memory Usage with Command Line Client

[rybobcat]

When checking my computer for the size of the result.txt file, I happen to notice that the amount of memory being used my the muon1 task (command line client) was at 157,696 KB and rising. I thought to myself, self, this is really high. So I stopped the task and then restarted the command line client again. The memory usage started around 55,000 KB.

I noticed that the memory usage kept on rising. This could be a possible memory leak and a cause for concern for those running the command line client for an extended period of time.

After further investigation, my P4 system is running the background task and it is steady at 88,000 KB. I also checked my dual Xeon system that is running the Command line client and it is > 228,000 KB.

I would suggest to those users running the Command line client to switch to the background client.

Please let me know if anyone else is noticing the same thing.:Q

 

[GunDog]

The memory usage does climb until it saves to the results file. then it starts low again raising until it saves to the results file again etc.
I thought it used alot of ram at first as well, but have plenty for it to use


Force

 

[rybobcat]

Wouldn't the auto-save lower your memory? I also noticed that the memory goes down once you send the results. I am caching the results for the Friday dump ( )

Thanks.

 

[BlackMountainCow]

That is really strange ... my muon1.exe CLI never goes over 30MB of memory usage even after a week without a reset. But I noticed that it gets higher and higher the more results u have in your results.dat as they are all loaded into RAM. I have 5000 here right now.

 

[GunDog]

I just watched mine again.
started out at 9 megs usage, climbed to 16 megs for a 301.1 Mpt result
saved to results.txt memory dropped to 9 megs again. It keeps the data in ram when it writes to the autosave file as well. the autosave is for if you close the app it will reload the data it was working on.

Nothing to worry about normal operation

Force