We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Ref: http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/4515/
I don't know any of druntime or vibe internals, so I have no idea how I can find out if this is expected.
I've located the slow code to be libevent2tcp.d -> leastSize -> mctx.core.yieldForEvent() -> Fiber.yield()
libevent2tcp.d -> leastSize -> mctx.core.yieldForEvent() -> Fiber.yield()
The text was updated successfully, but these errors were encountered:
Calling Fibers is pretty fast, around 60ns per call on my machine. It does trash the return stack of the CPU so there are some mispredictions.
import core.thread, std.datetime, std.stdio; void main() { scope fib = new Fiber({for (;;) Fiber.yield(); }); auto sw = StopWatch(AutoStart.yes); foreach (i; 0 .. 1_000_000) fib.call(); sw.stop(); writeln(sw.peek.usecs); }
Sorry, something went wrong.
This seems to be an instance of #338. Can you confirm that it runs fast again on the latest beta?
Closing until confirmed.
No branches or pull requests
Ref: http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/4515/
I don't know any of druntime or vibe internals, so I have no idea how I can find out if this is expected.
I've located the slow code to be
libevent2tcp.d -> leastSize -> mctx.core.yieldForEvent() -> Fiber.yield()
The text was updated successfully, but these errors were encountered: