On Monday, 16 March 2020 14:25:52 UTC+1, Nitish Saboo wrote: > > Hi, > > I upgraded the go version and compiled the binary against go version 'go > version go1.12.4 linux/amd64'. > I ran the program for some time. I made almost 30-40 calls to the method > Load_Pattern_Db(). > The program starts with 6% Mem Usage. The memory usage increases only when > I call 'LoadPatternDb()' method and LoadPatternDb() method is called by a > goroutine at regular intervals of 3 minutes(making use of ticker here ). > > What I observed is: > > 1)After almost 16-17 calls to the method 'LoadPatternDb(), the memory > usage got almost constant at 29%. But I did not expect the program to take > this much memory. > When I restart the service the Mem Usage again starts with 6%. > > a) Is this the sign of memory leaking? >
No, as explained above. > > b) Till this moment I did not see memory getting reclaimed or going down > but it did become constant. > As mentioned by experts above, the same sort of behavior is seen here. But > I did not expect the memory usage to grow this much. Is this expected? > Yes. (Well, no. But your gut feeling of how much memory should grow is not a suitable benchmark to compare actual growth to.) > > 2)I will run mem-profiling at intervals(10 minutes, 100 minutes..etc) as > mentioned in the earlier email. > > a) Which all mem-stats variables should I look into for debugging this > kind of behavior? > Alloc/HeapAlloc But probably this is plain useless as nothing here indicates that you do have any memory issues. V. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/e664151d-474d-4c1d-ae1d-979dc6975469%40googlegroups.com.
