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

Latency profiling support #3754

Merged
merged 18 commits into from
Oct 13, 2015
Merged

Latency profiling support #3754

merged 18 commits into from
Oct 13, 2015

Conversation

ctiller
Copy link
Member

@ctiller ctiller commented Oct 8, 2015

Got this up and running again, redid the script to generate something that's nice to look at in a browser.
Built out some wrappers to publish this stuff to Jenkins.

@@ -45,6 +45,8 @@
#include <grpc/support/log.h>
#include <grpc/support/useful.h>

#include "src/core/profiling/timers.h"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

included but not used?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@@ -199,11 +199,11 @@ static void tcp_continue_read(grpc_exec_ctx *exec_ctx, grpc_tcp *tcp) {
msg.msg_controllen = 0;
msg.msg_flags = 0;

GRPC_TIMER_BEGIN(GRPC_PTAG_RECVMSG, 0);
GPR_TIMER_BEGIN("recvmsg", 1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is "id" now 1? The corresponding END still has id==0

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed the meaning... getting rid of id and making this 'important' -- it turns out to be useful to have important start/end scopes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is only the begin marked as important, or the interval up to the _END? ie, when/why would one wanna set an _END as important?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, nevermind. it's all in the code :)

@dgquintas
Copy link
Contributor

LGTM. Firing up a round of Jenkins for good measure.

@ctiller
Copy link
Member Author

ctiller commented Oct 13, 2015

Green.

dgquintas added a commit that referenced this pull request Oct 13, 2015
@dgquintas dgquintas merged commit 93cec49 into grpc:master Oct 13, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Jan 29, 2019
@lock lock bot unassigned dgquintas Jan 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants