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

RPS mode data size feature #567

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

RPS mode data size feature #567

wants to merge 1 commit into from

Conversation

cvetkovic
Copy link
Contributor

No description provided.

Signed-off-by: Lazar Cvetković <[email protected]>
@leokondrashov
Copy link
Contributor

I see this data size is only applicable in RPS and HTTP invoker.

So, a couple of questions. Do we have or can we add comparable data movement for trace execution? The other question would be to find some dataset to make it realistic.

And what about RPC mode? We have a message in protobuf that we don't use at all; we can use it to model data movement.

@cvetkovic
Copy link
Contributor Author

@leokondrashov: There is an opportunity to add data movement for trace execution. This paper gives some insight into distribution and releases the trace. I think this could be nice project for a student to take care of -- look into the data, find a way to match functions in the execution trace with data trace, and add such a feature in loader.

Regarding the RPC mode, I can add support for it in gRPC. I think this will perform poorly with large data payloads (like 1MB and bigger), so I expect significant overhead there. What do you think?

@leokondrashov
Copy link
Contributor

The payloads are quite small in this paper, up to 10s KB in the majority of cases, so I don't see a problem with adding it to gRPC.

The other question is also how to interpret these numbers, they are not only about inputs that we send directly with the requests, but also outputs. Originally, it was intended more as a storage workload characterization, not data moved through HTTP with request/response.

Previously, @JooyoungPark73 was doing some work on that front with the Azure Blob trace you mentioned. I think we should have some discussion about that.

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