So far, to get things up and running, everything has been using fixed message sizes. We should modify the client to instead sample from some configurable distribution. This shouldn't be too difficult, but would entail:
sampling an int from the distribution and multiplying by a padding constant
For now, I think a single distribution is good enough. In the future, it's possible we should use different distributions for Active and Idle states, or taking into account the sizes of messages sent and received so far.
So far, to get things up and running, everything has been using fixed message sizes. We should modify the client to instead sample from some configurable distribution. This shouldn't be too difficult, but would entail:
- adding the parameter to the client config
- making [`construct_message`](https://git-crysp.uwaterloo.ca/j3tracey/MGen/src/4212301fce025c537460f289ed96eb91d07bf4ad/src/bin/client.rs#L439) take a size parameter or the distribution
- sampling an int from the distribution and multiplying by a padding constant
For now, I think a single distribution is good enough. In the future, it's possible we should use different distributions for Active and Idle states, or taking into account the sizes of messages sent and received so far.
So far, to get things up and running, everything has been using fixed message sizes. We should modify the client to instead sample from some configurable distribution. This shouldn't be too difficult, but would entail:
construct_messagetake a size parameter or the distributionFor now, I think a single distribution is good enough. In the future, it's possible we should use different distributions for Active and Idle states, or taking into account the sizes of messages sent and received so far.
Fixed via
a4272b771e