Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

website: profiling go programs blog post is out of date #3893

Closed
davecheney opened this issue Aug 1, 2012 · 20 comments
Closed

website: profiling go programs blog post is out of date #3893

davecheney opened this issue Aug 1, 2012 · 20 comments
Labels
Documentation Issues describing a change to documentation. FrozenDueToAge
Milestone

Comments

@davecheney
Copy link
Contributor

The blog post 

   http://blog.golang.org/2011/06/profiling-go-programs.html

refers to the older gopprof tool.

If possible, could the blog post be updated to use the new 
   
   go tool pprof 

syntax.
@robpike
Copy link
Contributor

robpike commented Aug 2, 2012

Comment 2:

Labels changed: added documentation.

Owner changed to @adg.

Status changed to Accepted.

@alexbrainman
Copy link
Member

Comment 3:

From https://golang.org/issue/3879?c=4:
>>> ... It'd be good to have a warning somewhere that mingw is recommended for pprof
under Win. ...
Alex

@mccoyst
Copy link
Contributor

mccoyst commented Sep 5, 2012

Comment 4:

Also, the pprof tool isn't mentioned in the docs for the go command or the runtime/pprof
package.

@rsc
Copy link
Contributor

rsc commented Sep 12, 2012

Comment 5:

Labels changed: added go1.1.

@minux
Copy link
Member

minux commented Nov 3, 2012

Comment 7:

I'd like to tackle this, has anyone started yet?
I plan to completely update the article (rerun all commands, and update all numbers)
and import it (along with all programs) into doc/articles, is it reasonable?

@adg
Copy link
Contributor

adg commented Nov 3, 2012

Comment 8:

Nobody has started with this yet. It would be great if you could do it.
Your suggested approach is perfect. Thank you!

@minux
Copy link
Member

minux commented Nov 4, 2012

Comment 9:

which version of go and g++ should i use?
i plan to use latest development snapshot of Go and lastest gcc snapshot (4.8.0).
(or go 1.0.3 vs. g++ 4.7.2?)
any opinions?

@adg
Copy link
Contributor

adg commented Nov 4, 2012

Comment 10:

Using go tip is a good idea.
I don't have a strong opinion on gcc version. Latest stable would make sense to me.

@bradfitz
Copy link
Contributor

bradfitz commented Jan 9, 2013

Comment 11:

Issue #4630 has been merged into this issue.

@rsc
Copy link
Contributor

rsc commented Jan 31, 2013

Comment 12:

Labels changed: added priority-later, removed priority-soon.

@rsc
Copy link
Contributor

rsc commented Mar 12, 2013

Comment 13:

Labels changed: added go1.1maybe, removed go1.1.

@robpike
Copy link
Contributor

robpike commented Mar 12, 2013

Comment 14:

minux, are you working on this? i think it's worth just fixing up the command syntax for
go1.1 and doing a rewrite later.

@minux
Copy link
Member

minux commented Mar 21, 2013

Comment 15:

yes, i was waiting for gcc 4.8.
now that gcc 4.8 is in prerelease and we're about to release Go 1.1,
it's time to update the benchmark data in that article.
will propose CL this weekend.
should i also update the copy of article in the go.blog sub-repo?

@adg
Copy link
Contributor

adg commented Mar 21, 2013

Comment 16:

Yes, in fact the go.blog subrepo is the new canonical location for the article, so feel
free to just update that one.

@minux
Copy link
Member

minux commented Mar 21, 2013

Comment 17:

so no need to import that article into doc/articles?

@adg
Copy link
Contributor

adg commented Mar 21, 2013

Comment 18:

Not at this stage. I intend to remove most of the articles from doc/articles and point
to the versions at blog.golang.org instead, and to also include a version of the blog
server in the binary distributions for offline viewing.

@minux
Copy link
Member

minux commented Mar 27, 2013

Comment 19:

https://golang.org/cl/7797046

@minux
Copy link
Member

minux commented Mar 27, 2013

Comment 20:

@rsc, do you want me to update files in the benchgraffiti project?
if yes, do i need to send a CL to golang-dev?

@robpike
Copy link
Contributor

robpike commented May 18, 2013

Comment 21:

Labels changed: added go1.2maybe, removed go1.1maybe.

@minux
Copy link
Member

minux commented Jun 2, 2013

Comment 22:

This issue was closed by revision golang/blog@bbba492.

Status changed to Fixed.

@davecheney davecheney added fixed Documentation Issues describing a change to documentation. labels Jun 2, 2013
@rsc rsc added this to the Go1.2 milestone Apr 14, 2015
@rsc rsc removed the go1.2maybe label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
omunroe-com pushed a commit to omunroe-com/gogooblg that referenced this issue Nov 12, 2018
Fixes golang/go#3893.

R=adg, r, rsc, tracey.brendan, remyoudompheng, a2800276, arnehormann, jonathan, dave, go.peter.90, christoph
CC=golang-dev
https://golang.org/cl/7797046
gopherbot pushed a commit to golang/website that referenced this issue May 26, 2021
Fixes golang/go#3893.

R=adg, r, rsc, tracey.brendan, remyoudompheng, a2800276, arnehormann, jonathan, dave, go.peter.90, christoph
CC=golang-dev
https://golang.org/cl/7797046
X-Blog-Commit: bbba49261a91e795ba687151099924acb4dad40e
@rsc rsc unassigned adg Jun 22, 2022
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
Fixes golang/go#3893.

R=adg, r, rsc, tracey.brendan, remyoudompheng, a2800276, arnehormann, jonathan, dave, go.peter.90, christoph
CC=golang-dev
https://golang.org/cl/7797046
X-Blog-Commit: bbba49261a91e795ba687151099924acb4dad40e
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation Issues describing a change to documentation. FrozenDueToAge
Projects
None yet
Development

No branches or pull requests

9 participants