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

tagfocus issues with size #153

Closed
ahh opened this issue Jul 7, 2017 · 4 comments
Closed

tagfocus issues with size #153

ahh opened this issue Jul 7, 2017 · 4 comments
Assignees

Comments

@ahh
Copy link
Contributor

ahh commented Jul 7, 2017

(again, silly zipped profile for github naming)

pprof -raw heapz
Samples:
objects/count space/bytes[dflt]
       7438   60936269: 1 2 3 4 5 6
                bytes:[8192] request:[8191]
        238   62466710: 7 8 9 10 5 6
                bytes:[262144] request:[262143]
       3341   54739221: 7 8 9 10 5 6
                bytes:[16384] request:[16383]
       2064   67634517: 1 2 3 4 5 6
                bytes:[32768] request:[32767]
      29710   60847108: 1 2 3 4 5 6
                bytes:[2048] request:[2047]
        396   51920894: 1 2 3 4 5 6
                bytes:[131072] request:[131071]
      63503   65027585: 7 8 9 10 5 6
                bytes:[1024] request:[1023]
       1105   72423082: 7 8 9 10 5 6
                bytes:[65536] request:[65535]
        108   56884975: 11 12 13 3 4 5 6
                bytes:[524288] request:[524287]
      15887   65075220: 7 8 9 10 5 6
                bytes:[4096] request:[4095]

Now let's try to filter to some of these. Each of the below queries should match exactly one entry and do (this is good)

pprof -traces -tagfocus=4096bytes heapz
pprof -traces -tagfocus=4095request heapz
pprof -traces -tagfocus=4kb heapz
pprof -traces -tagfocus=512kb heapz
pprof -traces -tagfocus=524288bytes: heapz

But this matches everything:

pprof -traces -tagfocus=512kb: heapz

Note that 524288 bytes = 512kb. But for some reason when we have a non-empty range that breaks. That's a flat bug. :1kb seems to work, otoh, as does 1kb:4kb.

A slightly different problem is that there's no easy way to specify request ranges without having to write out full numbers. I'd be very happy if I could specify, say:

-tagfocus=/request/256kb:512kb

to mean "I want to see a tag, whose name matches "request", whose value is between 256kb and 512kb.

heapz.zip

@aalexand
Copy link
Collaborator

@nolanmar511 Is this issue still relevant?

@nolanmar511
Copy link
Contributor

It's still not resolved, but I think it should be fixed when/by adding units to tags.

@aalexand
Copy link
Collaborator

aalexand commented Oct 4, 2017

@nolanmar511 Should we mark this issue as fixed now?

@nolanmar511
Copy link
Contributor

I think so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants