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

Issue 56 track unacked; added option to disable connection pooling #59

Closed

Conversation

claudiofahey
Copy link

This PR includes various unrelated updates. Let me know if you need these as separate issues, branches, and PRs.

  • Number of unacked events and bytes are now periodically printed
  • Added Dockerfile and Kubernetes job
  • Removed createScope to allow this to run in Nautilus
  • Added option to disable connection pooling for producers
  • Statistics are now logged using the slf4j logger so that timestamps are printed

Claudio Fahey added 5 commits September 4, 2019 20:11
…nted

Signed-off-by: Claudio Fahey <claudio.fahey@dell.com>
Signed-off-by: Claudio Fahey <claudio.fahey@dell.com>
Signed-off-by: Claudio Fahey <claudio.fahey@dell.com>
Signed-off-by: Claudio Fahey <claudio.fahey@dell.com>
…re printed

Signed-off-by: Claudio Fahey <claudio.fahey@dell.com>
}

@Override
public long recordWrite(byte[] data, TriConsumer record) {
CompletableFuture ret;
final long time = System.currentTimeMillis();
record.accept(time, -1, data.length);
Copy link
Contributor

Choose a reason for hiding this comment

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

This will reduce the strength of the tool to pump more data to pravega client; this command method is used kafka bench-marking too.
implement it as different method something like "recordWriteAck" and invoke when the user specifies the "-unack true" .

Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @claudiofahey
I have raised the pull request : #61
to extend the tool for kafka bench-marking; if you are make any changes in the tool ; I suggest you test with kafka too; This bench-marking tool and existing kafka benchmark tool should yield same results for the single producer.

Copy link
Author

Choose a reason for hiding this comment

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

I will update the PR once #61 has been merged to master.

@claudiofahey
Copy link
Author

I will resubmit this PR later.

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