Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFix benchmarks with `OsIpcReceiver` not being `Sync` anymore #122
Conversation
|
This supersedes #121 (Well, at least I think it's a preferable fix...) Would be great if someone with a more modern system (or maybe even a different OS?) could check whether the second patch produces a visible difference -- especially in the threaded case (i.e. |
|
I just tested with and without this -- the big data benchmark numbers definitely change, e.g. from:
to
But not enough to care I don't think. We should still land this, as without it it's impossible to benchmark.. if someone wants to have more precise benchmarking they can work on that afterwards. |
|
These are the latest Windows numbers, from my laptop (past thing was from a desktop). Second numbers look fine. Before Sync change:
After first patch:
After second patch:
|
|
So just like on Linux, there is a lot of fluctuation in the threaded tests. I suspect the lower numbers for 128k and 256k in the last run are also just a random fluctuation rather than actually better results? At any rate, it doesn't look like either variant actually makes things worse :-) |
|
I decided to drop the second patch, as it's really an unrelated change -- so this is just a trivial fix now. |
|
@bors-servo r+ |
|
|
Fix benchmarks with `OsIpcReceiver` not being `Sync` anymore The first commit is the minimal fix to get it working again. The second patch switches to a different thread handling approach, which inexplicably produces lower overhead in some (unrelated) cases on my system...
|
|
antrik commentedNov 12, 2016
The first commit is the minimal fix to get it working again.
The second patch switches to a different thread handling approach, which inexplicably produces lower overhead in some (unrelated) cases on my system...