No problems! If I can get a beta running I'll revisit this thread.
Cheers,
On Tue, Dec 5, 2017, 19:41 Rick Hudson wrote:
> Henrik,
> Thanks for the kind offer but there isn't much the runtime team can do
> with the logs since 1.9 isn't likely to be changed due to this issue.
>
>
>
> On Tue, Dec
Henrik,
Thanks for the kind offer but there isn't much the runtime team can do with
the logs since 1.9 isn't likely to be changed due to this issue.
On Tue, Dec 5, 2017 at 10:43 AM, Henrik Johansson
wrote:
> I would gladly help with this but afaik Heroku only makes stable versions
> available:
I would gladly help with this but afaik Heroku only makes stable versions
available:
https://github.com/heroku/heroku-buildpack-go/blob/master/data.json
I guess I could deploy a docker container but I don't know if it changes
everything and I doubt I have time before christmas at least.
Maybe some
Glad to have helped. The runtime team would be interested in seeing what
these pauses look like in the beta. If you have the time could you send
them to us after the beta comes out.
On Tue, Dec 5, 2017 at 9:06 AM, Henrik Johansson
wrote:
> Ok so it's not bad, thats good!
>
> The inital ~20 sec
Ok so it's not bad, thats good!
The inital ~20 sec numbers come from the graphs that Herokus Go Metrics
(Beta) provides.
These must be sums in the given graph bucket which may for a 24H period add
up to the high numbers I guess.
I will let it run over night and see what it looks like tomorrow, th
The wall clock is the first set of numbers, the second set is CPU. So 8P
running for 8ms wall clock will result in 64ms CPU. The word "wall" was
dropped to keep the line short.
There will be a beta out in the proverbial next few days that could help
reduce even these STW times. The original pos
I am watching with childlike fascination...
This is interesting perhaps:
gc 130 @2834.158s 0%: 0.056+3.4+2.9 ms clock, 0.45+2.8/5.6/0+23 ms cpu,
8->8->4 MB, 9 MB goal, 8 P
gc 131 @2834.178s 0%: 0.023+7.3+0.12 ms clock, 0.18+1.2/5.4/9.2+1.0 ms cpu,
9->9->5 MB, 10 MB goal, 8 P
---> gc 132 @2836.882
Oh yeah, I forgot someone added that a while back. That should work.
On Tue, Dec 5, 2017 at 6:23 PM, Henrik Johansson wrote:
> So it has to run the program? I thought I saw "logfile" scenario in the
> examples?
>
> GODEBUG=gctrace=1 godoc -index -http=:6060 2> stderr.log
> cat stderr.log | gcvis
So it has to run the program? I thought I saw "logfile" scenario in the
examples?
GODEBUG=gctrace=1 godoc -index -http=:6060 2> stderr.log
cat stderr.log | gcvis
I have shuffled the Heroku logs into Papertrail so I should be able to
extract the log lines from there.
tis 5 dec. 2017 kl 08:10 skr
Probably not for your scenario, gcviz assumes it can run your program
as a child.
On Tue, Dec 5, 2017 at 6:07 PM, Henrik Johansson wrote:
> I found https://github.com/davecheney/gcvis from +Dave Cheney is it a good
> choice for inspecting the gc logs?
>
> tis 5 dec. 2017 kl 07:57 skrev Henrik Joh
I found https://github.com/davecheney/gcvis from +Dave Cheney
is it a good choice for inspecting the gc logs?
tis 5 dec. 2017 kl 07:57 skrev Henrik Johansson :
> I have just added the gc tracing and it looks like this more or less all
> the time:
>
> gc 78 @253.095s 0%: 0.032+3.3+0.46 ms clock,
I have just added the gc tracing and it looks like this more or less all
the time:
gc 78 @253.095s 0%: 0.032+3.3+0.46 ms clock, 0.26+0.24/2.6/2.4+3.6 ms cpu,
11->12->4 MB, 12 MB goal, 8 P
gc 79 @253.109s 0%: 0.021+2.1+0.17 ms clock, 0.16+0.19/3.6/1.2+1.3 ms cpu,
9->9->4 MB, 10 MB goal, 8 P
gc 80 @
I am sorry, I was unclear. The app uses very little ram but the provisioned
available memory is 512 MB.
I will try to experiment with GC toggles as you suggest and report back.
Thx!
On Sat, Dec 2, 2017, 22:18 rlh via golang-nuts
wrote:
> Hard telling what it going on. 35MB, even for 1 CPU, see
Hard telling what it going on. 35MB, even for 1 CPU, seems very small. Most
modern system provision more than 1GB per HW thread though I've seen some
provision as little as 512MB. GOGC (SetGCPercent) can be adjust so that the
application uses more of the available RAM. Running with GODEBUG=gctra
14 matches
Mail list logo
