Memory Issues with ListUsers about madmin-go HOT 7 CLOSED

I was able to lower memory consumption by setting a lower value for the GOGC env variable. My knowledge of the Go garbage collection is not sufficient to know whether this is still an issue or intended behaviour.

from madmin-go.

@robbertvdg Alloc numbers is typically the total amount allocated, look at Heap In Use.

This looks like intended behavior, but you didn't share the PrintMemUsage(), I cannot know.

from madmin-go.

Looking at the function, there is nothing there that can really be an issue.

from madmin-go.

The function:

func PrintMemUsage() {
	var m run.MemStats
	run.ReadMemStats(&m)
	// For info on each, see: https://golang.org/pkg/runtime/#MemStats
	fmt.Printf("Alloc = %v MiB", bToMb(m.Alloc))
	fmt.Printf("\tTotalAlloc = %v MiB", bToMb(m.TotalAlloc))
	fmt.Printf("\tSys = %v MiB", bToMb(m.Sys))
	fmt.Printf("\tNumGC = %v\n", m.NumGC)
}

from madmin-go.

Including m.HeapInUse:

heap = 72 MiB Alloc = 69 MiB TotalAlloc = 159 MiB Sys = 140 MiB NumGC = 13
heap = 107 MiB Alloc = 103 MiB TotalAlloc = 230 MiB Sys = 207 MiB NumGC = 14
heap = 171 MiB Alloc = 167 MiB TotalAlloc = 294 MiB Sys = 273 MiB NumGC = 14
heap = 171 MiB Alloc = 167 MiB TotalAlloc = 294 MiB Sys = 273 MiB NumGC = 14
heap = 171 MiB Alloc = 167 MiB TotalAlloc = 294 MiB Sys = 273 MiB NumGC = 14
heap = 235 MiB Alloc = 231 MiB TotalAlloc = 358 MiB Sys = 339 MiB NumGC = 15
heap = 235 MiB Alloc = 231 MiB TotalAlloc = 358 MiB Sys = 339 MiB NumGC = 15
heap = 299 MiB Alloc = 295 MiB TotalAlloc = 422 MiB Sys = 405 MiB NumGC = 15
heap = 363 MiB Alloc = 359 MiB TotalAlloc = 486 MiB Sys = 471 MiB NumGC = 15
heap = 363 MiB Alloc = 359 MiB TotalAlloc = 486 MiB Sys = 471 MiB NumGC = 15
Cycle completed
heap = 363 MiB Alloc = 359 MiB TotalAlloc = 487 MiB Sys = 471 MiB NumGC = 15
heap = 427 MiB Alloc = 423 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 427 MiB Alloc = 423 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 427 MiB Alloc = 423 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 427 MiB Alloc = 423 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 428 MiB Alloc = 423 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 428 MiB Alloc = 423 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 428 MiB Alloc = 424 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 428 MiB Alloc = 424 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15
heap = 428 MiB Alloc = 424 MiB TotalAlloc = 551 MiB Sys = 537 MiB NumGC = 15

from madmin-go.

Not really seeing any leak there.

Yes, the function could have pagination so a huge number of users don't take too much memory, but this is not really something that seems to worrysome.

from madmin-go.

Not really seeing any leak there.

Yes, the function could have pagination so a huge number of users don't take too much memory, but this is not really something that seems to worrysome.

Yeah this looks like normal and will be relinquished properly to Go runtime as needed.

from madmin-go.