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

Revert "Remove exception parameterisation from serialisation (#2524)" #2752

Merged
merged 1 commit into from
Jun 6, 2018

Conversation

JONBRWN
Copy link
Contributor

@JONBRWN JONBRWN commented Jun 6, 2018

This reverts commit d34dce6.

While performance testing the Pony version of Wallaroo's Market Spread
application in a multi worker scenario, it was discovered that the above
commit introduced a performance regression in both throughput and latency.
This regression is not present in a single worker run where serialisation
is not used. It should be noted that this regression only occurs when
consuming messages at a maximum rate and is not present if the sending
worker is not performing at maximum capacity. With this commit reverted,
sending in messages at the same rate resulted in higher throughput
and lower latencies.

If an example application is needed to recreate this behavior we can
provide instructions to run the Wallaroo application or attempt to
create a minimal example.

…g#2524)"

This reverts commit d34dce6.

While performance testing the Pony version of Wallaroo's Market Spread
application in a multi worker scenario, it was discovered that the above
commit introduced a performance regression in both throughput and latency.
This regression is not present in a single worker run where serialisation
is not used. It should be noted that this regression only occurs when
consuming messages at a maximum rate and is not present if the sending
worker is not performing at maximum capacity. With this commit reverted,
sending in messages at the same rate resulted in higher throughput
and lower latencies.

If an example application is needed to recreate this behavior we can
provide instructions to run the Wallaroo application or attempt to
create a minimal example.
@winksaville
Copy link
Contributor

It would be nice to have latency and throughput tests so performance regressions can be caught early.

@SeanTAllen
Copy link
Member

@Praetonus just heads up we are reverting this for now due to the "we arent sure why this caused a regression".

@SeanTAllen SeanTAllen mentioned this pull request Jun 6, 2018
@SeanTAllen SeanTAllen merged commit e52ef29 into ponylang:master Jun 6, 2018
SeanTAllen added a commit that referenced this pull request Jun 6, 2018
dipinhora pushed a commit to dipinhora/ponyc that referenced this pull request Jun 7, 2018
dipinhora pushed a commit to dipinhora/ponyc that referenced this pull request Jun 8, 2018
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.

4 participants