Skip to content

feature: supported to measure the distribution of the VFS read/write … - #36

Open
membphis wants to merge 5 commits into
openresty:masterfrom
membphis:disk-io-blocking
Open

feature: supported to measure the distribution of the VFS read/write …#36
membphis wants to merge 5 commits into
openresty:masterfrom
membphis:disk-io-blocking

Conversation

@membphis

@membphis membphis commented Feb 26, 2018

Copy link
Copy Markdown

…latency.

todo:

  • add doc for script samples/disk-io-blocking-vfs.sxx

Comment thread samples/disk-io-blocking-vfs.sxx Outdated

probe vfs.read*.return, vfs.write*.return
{
if (sprintf("%d", pid()) =~ "^($^target)$" && begin[pid()] > 0) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is slow: see how we do this in the ngx-req-distr tool.

Comment thread stap++ Outdated

$StdVars{pid_ok} = gen_pid_test_condition(\@pids);
$StdVars{target} = "@pids";
$StdVars{target} = join "|", @pids;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

No, we don't want this change.

@membphis

membphis commented Mar 4, 2018

Copy link
Copy Markdown
Author

@agentzh all fixed, please take a look when you have time ^_^

@membphis

membphis commented Mar 4, 2018

Copy link
Copy Markdown
Author

one more thing, I rewrite samples/ngx-req-latency-distr.sxx.

It supported to monitor the master process and get all the metric of worker process, and supported time, method and uri argument now.

Comment thread README.markdown Outdated

[Back to TOC](#table-of-contents)

disk-io-blocking-vfs

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

The tool name is too verbose. vfs means virtual file system, which already implies disk I/O. Also, you are actually testing file IO instead of disk IO since there is no way to know if it indeed touches the disk device on the VFS level.

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

Successfully merging this pull request may close these issues.

2 participants