Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(236)

Issue 5754047: code review 5754047: build: use run.go for running tests (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
13 years, 2 months ago by rsc
Modified:
13 years, 2 months ago
Reviewers:
minux1
CC:
golang-dev, bradfitz
Visibility:
Public.

Description

build: use run.go for running tests Also, tweak run.go to use no more than 2x the number of CPUs, and only one on ARM. 53.85u 13.33s 53.69r ./run 50.68u 12.13s 18.85r go run run.go Fixes issue 2833.

Patch Set 1 #

Patch Set 2 : diff -r 0b8f3af00b0e https://code.google.com/p/go/ #

Patch Set 3 : diff -r 0b8f3af00b0e https://code.google.com/p/go/ #

Patch Set 4 : diff -r 536be3c2a16a https://code.google.com/p/go/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+14 lines, -4 lines) Patch
M src/run.bash View 1 1 chunk +1 line, -1 line 0 comments Download
M src/run.bat View 1 1 chunk +8 lines, -1 line 0 comments Download
M test/run.go View 1 2 2 chunks +5 lines, -2 lines 0 comments Download

Messages

Total messages: 4
rsc
Hello golang-dev@googlegroups.com, I'd like you to review this change to https://code.google.com/p/go/
13 years, 2 months ago (2012-03-06 03:26:02 UTC) #1
bradfitz
LGTM "Fixes issue 2833" On Mon, Mar 5, 2012 at 7:26 PM, <rsc@golang.org> wrote: > ...
13 years, 2 months ago (2012-03-06 03:38:50 UTC) #2
rsc
*** Submitted as 603ac92ed3a7 *** build: use run.go for running tests Also, tweak run.go to ...
13 years, 2 months ago (2012-03-06 03:47:26 UTC) #3
minux1
13 years, 2 months ago (2012-03-06 14:22:05 UTC) #4
On Tue, Mar 6, 2012 at 11:47 AM, <rsc@golang.org> wrote:
>
>  build: use run.go for running tests
>
> Also, tweak run.go to use no more than 2x the
> number of CPUs, and only one on ARM.
>
The Linux/ARM builder has two CPU cores, and currently this part of test
takes most of the
time. I believe it will receive some speedup if we set it to runtime.NumCPU()
instead of 1
(it certainly won't hurt ARM machines with only 1 core, but it will speed
up the multicore
machines.)

Some statistics on idle builder with tmpfs holding ~/work2:
minux@omap4460:~/work2/go/test$ /usr/bin/time go run run.go -n=4
290.89user 37.23system 2:53.16elapsed 189%CPU (0avgtext+0avgdata
304368maxresident)k
0inputs+0outputs (0major+3202559minor)pagefaults 0swaps

minux@omap4460:~/work2/go/test$ /usr/bin/time go run run.go -n=3
289.71user 36.03system 2:51.91elapsed 189%CPU (0avgtext+0avgdata
304448maxresident)k
0inputs+0outputs (0major+3195588minor)pagefaults 0swaps

minux@omap4460:~/work2/go/test$ /usr/bin/time go run run.go -n=2
288.66user 35.11system 2:52.45elapsed 187%CPU (0avgtext+0avgdata
304368maxresident)k
0inputs+0outputs (0major+3192096minor)pagefaults 0swaps

minux@omap4460:~/work2/go/test$ /usr/bin/time go run run.go -n=1
290.06user 35.67system 5:31.61elapsed 98%CPU (0avgtext+0avgdata
304368maxresident)k
0inputs+0outputs (0major+3179289minor)pagefaults 0swaps

minux@omap4460:~/work2/go/test$ /usr/bin/time ./run &>/dev/null
263.31user 36.98system 5:28.20elapsed 91%CPU (0avgtext+0avgdata
1165424maxresident)k
0inputs+0outputs (0major+3948024minor)pagefaults 0swaps

I've made a CL for this: http://codereview.appspot.com/5753054.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b