Hello! "Real" is what I see in atop/htop/ps, as i mentioned erlier.
Yep, about asked memory from OS is in my mind too, but how can I find situation when/why it's occur? To be more precise, my app load N merabytes from DB, and put them into map. So, I fully understand when N megabytes transform to N gigabytes in memory in map, in the next iteration, after some time, my app doing load and transform again, so, I can imagine situation, when in exist two maps, N gigabytes each, but after that old map is gone, and my app start using new map! So, in my mind GC shoud kill old map, is I'm right? I How can I tune memory allocator? May be I can tune it to allocate memory more tight? Why my app don't return back allocated memory? вторник, 22 ноября 2016 г., 0:10:20 UTC+3 пользователь Tamás Gulácsi написал: > > What is "real"? > 65Gb has been asked from the OS, and it gave that much to the runtime. But > it used only 25Gb of it. > Maybe even released some to the OS, but maybe that did not took that. > > Is the 25Gb really needed and used for good? The OOM suggests that for > moments your program allocated much more.... > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
