Different result first time I run profmem...

[henrikbengtsson]

Different result first time I run profmem...

[HenrikBengtsson]

Better late than never. Two comments:

Yes, when you start a fresh R session, there are things that will be additional things that will allocated the first time you evaluate some code. Thus, you often have to call it more than ones to get a good better idea about what's going on in your code. I don't fully understand exactly what is going on under the hood in R here, but if one would understand it better, maybe one could create a profmem::burnin() function that one can call once to fix this. Maybe it could even be done automagically by the profmem package, so the user does not have to do anything.

In this example memory usage increases while in my case it decreases a lot. Which one would be the "real" memory use, the first one or the following ones?

So, please note that utils::Rprofmem(), and therefore also profmem::profmem(), does not log memory deallocations, cf. https://github.com/HenrikBengtsson/profmem#what-is-logged. Because of this, you cannot use these data to figure out the amount of memory currently allocated, i.e. total() only reports on the total amount of allocations. FWIW, I've added it to the wishlist to have utils::Rprofmem() record also deallocations, c. HenrikBengtsson/Wishlist-for-R#25.