| Thread overview | |||||
|---|---|---|---|---|---|
|
January 21, 2012 Can gc_stats be exposed through core.memory? | ||||
|---|---|---|---|---|
| ||||
With a big fat "subject to change use at own risk" warning attached? | ||||
January 21, 2012 Re: Can gc_stats be exposed through core.memory? | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Bernard Helyer | On 21-01-2012 23:24, Bernard Helyer wrote: > With a big fat "subject to change use at own risk" warning attached? Would also like to have this. -- - Alex | |||
January 21, 2012 Re: Can gc_stats be exposed through core.memory? | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Bernard Helyer | Am 21.01.2012, 23:24 Uhr, schrieb Bernard Helyer <b.helyer@gmail.com>: > With a big fat "subject to change use at own risk" warning attached? Hey, I just had a use for that the other day. Then again on Linux >= 2.6.32, I can get at the all-time maximum memory usage as measured by the OS: http://linux.die.net/man/2/getrusage (or use the Windows counter part: http://msdn.microsoft.com/en-us/library/ms683219(v=vs.85).aspx) Often this is the information you really want. | |||
Copyright © 1999-2021 by the D Language Foundation
Permalink
Reply