New benchmarks in java #222
Open
mahlashrifi wants to merge 26 commits intospcl:java_benchmarks_supportfrom
Open
New benchmarks in java #222mahlashrifi wants to merge 26 commits intospcl:java_benchmarks_supportfrom
mahlashrifi wants to merge 26 commits intospcl:java_benchmarks_supportfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I hope you are doing well. I have made a pull request to clarify which parts are unnecessary and which parts need to be added.
This pull request contains three components:
1- Completion of Java support for benchmarking on OpenWhisk (when the fat jar, including wrapper and source code, is less than 48 MB).
The initial commits are included in this pull request.
2- Two new benchmarks:
Training function of TeaStore
CheckLogin benchmark of TeaStore
3- Six additional benchmarks that are essentially variations of CheckLogin with different dependencies. I noticed something called "payload" in the results of running SeBS benchmarks, but I wasn’t sure how to use it. These six benchmarks were meant to serve as examples for using our implementation. My intention was to test whether the jar file size directly affects the delay in running serverless functions, but I found no significant impact.
The attached diagram and summarized information provide further details. I believe that if we can set the payload in SeBS, these additional codes can be omitted.