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

Add document for subpartition runtime #231

Merged
merged 2 commits into from
Mar 28, 2024
Merged

Conversation

kawamuray
Copy link
Member

Also piggy-back benchmark addition for the virtual thread runtime.

Copy link
Member

@ocadaruma ocadaruma left a comment

Choose a reason for hiding this comment

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

Nice. Left one feedback

--param=decaton.subpartition.runtime=THREAD_POOL
----

image::runtime-benchmark-conc-peak.png[]
Copy link
Member

Choose a reason for hiding this comment

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

Though I understand that the focus of this appendix is about throughput-cap, I guess this graph might make confusing impression because 30000 with 20ms (4ms * 5) latency is still higher than vthread throughput shown in above graph. (So people may think "Got it, threadpool-runtime throughput will be capped by 30000 in 20ms-latency scenario. But vthread-runtime can't achieve 30000 in the first place....")

Isn't it better to show throughput cap with more high simulated latency like 100ms?

Copy link
Member

Choose a reason for hiding this comment

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

Hm, changed my mind.
Maybe I'm worrying too much. LGTM

@ocadaruma ocadaruma merged commit 479f043 into line:master Mar 28, 2024
5 checks passed
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