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

Why ThreadHints.onSpinWait() is not added for SleepingWaitStrategy #306

Open
justinplus opened this issue Sep 27, 2020 · 1 comment
Open

Comments

@justinplus
Copy link

Hi,

Just noticed that ThreadHints.onSpinWait() is not added for SleepingWaitStrategy.
https://github.com/LMAX-Exchange/disruptor/blob/master/src/main/java/com/lmax/disruptor/SleepingWaitStrategy.java#L83

private int applyWaitMethod(final SequenceBarrier barrier, int counter)
        throws AlertException
    {
        barrier.checkAlert();

        if (counter > 100)
        {
            --counter;
            // added
            ThreadHints.onSpinWait()
        }
...

Is this intended?

Thank you,
Justin

Palmr added a commit to Palmr/disruptor that referenced this issue Oct 18, 2020
…et called when we busy spin in SleepingWaitStrategy; But also all of the other wait strategies
@Palmr
Copy link
Contributor

Palmr commented Nov 7, 2020

Hi Justin,

This is a fair question, and one I don't think anyone has an answer for.
I looked around the codebase and many implementations of WaitStrategy have a busy-spin component where the thread hint could be applied.

While the code compiles and runs with the thread hint in what seem like appropriate places, I think we would need a benchmark to prove they provide some benefit and more importantly that they don't come at a cost.

I will leave this ticket open as benchmarks are something currently being worked upon in the Disruptor, and I would welcome any benchmarks or experimental data on this in the mean time.

Thanks,
Nick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants