You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
I'd like a section, maybe PERFORMANCE.md or in DISCUSSION.md, which explains the performance goals of this spec, and open areas which can help bridge the gap with native.
It'll be useful to evaluate the design, and point developers who have existing code so they can understand what performance to expect from:
The current spec.
Future revisions.
Executing SAB code on different platforms.
For example:
Hazard Pointer or RCU won't perform well on weak order machines, but neither will they with C++ consume.
seqlock will likely have suboptimal behavior.
Acquire/release operations are missing (affecting e.g. mutex), but should be readily available in the future.
This can't be exhaustive, but would be useful in developing benchmarks for SAB, and helping developers try it out (especially, setting expectations).
The text was updated successfully, but these errors were encountered:
OK, good point. Some of what you're suggesting is out of scope for DISCUSSION.md (certainly "future work" would be completely speculative and does not belong there) but these points could be made:
cost of seq_cst atomics
why no acquire/release or relaxed
If you want to contribute a PERFORMANCE.md document that goes beyond that I'm happy to accept it.
I'd like a section, maybe
PERFORMANCE.md
or inDISCUSSION.md
, which explains the performance goals of this spec, and open areas which can help bridge the gap with native.It'll be useful to evaluate the design, and point developers who have existing code so they can understand what performance to expect from:
For example:
This can't be exhaustive, but would be useful in developing benchmarks for SAB, and helping developers try it out (especially, setting expectations).
The text was updated successfully, but these errors were encountered: