<div dir="ltr">For what it's worth, I've been using DispatchQueue.concurrentPerform on my own projects that run on both Darwin and Linux and it's worked well for both. I haven't noticed the issue you're describing.<div><br></div><div>Perhaps you could include a repro case that demonstrates this behavior?</div><div><br></div><div>PS: However, my Swift CLI executables that use this are much slower on Linux, but that's more due to corelibs Foundation than anything related to Dispatch.</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, 28 Nov 2017 at 02:55 Spencer Kohan via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I did some performance testing, and found that while using concurrentPerform for a set of long running operations resulted in half the execution time of synchronous code on macOS, on Linux the execution time was not meaningfully different from the synchronous version. Is this expected?<div><br></div><div>Cheers,</div><div>Spencer Kohan</div></div>
_______________________________________________<br>
swift-corelibs-dev mailing list<br>
<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br>
</blockquote></div>