Re: [go-nuts] Re: go process memory limits and gurantees

2016-08-09 Thread gaurav
ould it would have helped here? I think this is what you were mentioning above? > > > *From: *> on behalf of gaurav < > gaurava...@gmail.com > > *Date: *Tuesday, August 9, 2016 at 7:17 AM > *To: *golang-nuts > > *Subject: *[go-nuts] Re: go process memory limits a

Re: [go-nuts] Re: go process memory limits and gurantees

2016-08-09 Thread Michael Jones
difficult to obtain so testing against it is hard. From: on behalf of gaurav Date: Tuesday, August 9, 2016 at 7:17 AM To: golang-nuts Subject: [go-nuts] Re: go process memory limits and gurantees Thank you for the confirmation! Wonder if I am approaching the problem in a wrong way? How

[go-nuts] Re: go process memory limits and gurantees

2016-08-09 Thread gaurav
Thank you for the confirmation! Wonder if I am approaching the problem in a wrong way? How is memory sizing usually done for Go applications - if one is not willing to allocate 2X of the process (real) memory needs? On Tuesday, August 9, 2016 at 8:15:37 AM UTC+5:30, bronze man wrote: > > I do n

[go-nuts] Re: go process memory limits and gurantees

2016-08-08 Thread bronze man
I do not find this kind of api in golang. If you found one,please tell me. The best you can do is that calling debug.SetGCPercent(10) to tell golang gc quicker, calling debug.FreeOsMemory() every second to free os memory faster and trying to reduce memory alloc number and size. On Sunday, Augu