<div dir="ltr">Hi Edsko, <div><br></div><div>Can you explain the figure linked to on that page a bit? E.g. how should the axes be labelled? </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 9:33 AM, Edsko de Vries <span dir="ltr"><<a href="mailto:edsko@well-typed.com" target="_blank">edsko@well-typed.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<div><br></div><div>Just for clarity's sake (as the author of that "Latency" section that Tim referred to): I have addressed all of the issues listed there in Network.Transport.TCP, with the exception of the first (the -threaded issue). As Tim points out, this is not a Cloud Haskell specific issue; I have written this up as a short blog post at <a href="http://www.edsko.net/2013/02/06/performance-problems-with-threaded" target="_blank">http://www.edsko.net/2013/02/06/performance-problems-with-threaded</a> .</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Edsko</div><div><br></div></font></span><div><div class="im"><br><br>On Wednesday, 6 February 2013 14:09:22 UTC, Tim Watson wrote:</div><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Hi Kostirya,
<br>
<br>I'm putting the parallel-haskell and ghc-users lists on cc, just in case other (better informed) folks want to chip in here.
<br>
<br>----
<br>
<br>First of all, I'm assuming you're talking about network latency when compiling with -threaded - if not I apologise for misunderstanding!
<br>
<br>There is apparently an outstanding network latency issue when compiling with -threaded, but according to a conversation I had with the other developers on #haskell-distributed, this is not something that's specific to Cloud Haskell. It is something to do with the threaded runtime system, so would need to be solved for GHC (or is it just the Network package!?) in general. Writing up a simple C program and equivalent socket use in Haskell and comparing the latency using -threaded will show this up.
<br>
<br>See the latency section in <a href="http://haskell-distributed.github.com/wiki/networktransport.html" target="_blank">http://haskell-distributed.<u></u>github.com/wiki/<u></u>networktransport.html</a> for some more details. According to that, there *are* some things we might be able to do, but the 20% latency isn't going to change significantly on the face of things.
<br>
<br>We have an open ticket to look into this (<a href="https://cloud-haskell.atlassian.net/browse/NTTCP-4" target="_blank">https://cloud-haskell.<u></u>atlassian.net/browse/NTTCP-4</a>) and at some point we'll try and put together the sample programs in a github repository (if that's not already done - I might've missed previous spikes done by Edsko or others) and investigate further.
<br>
<br>One of the other (more experienced!) devs might be able to chip in and proffer a better explanation.
<br>
<br>Cheers,
<br>Tim
<br>
<br>
<br></div><div><div class="h5">On 6 Feb 2013, at 13:27, <a>kost...@gmail.com</a> wrote:
<br>
<br>> Haven’t you had a necessity to launch Haskell in no-threaded mode during the intense network data exchange?
<br>> I am getting the double performance penalty in threaded mode. But I must use threaded mode because epoll and kevent are available in the threaded mode only.
<br>>
<br>
<br>[snip]
<br>
<br>>
<br>>
<br>> среда, 6 февраля 2013 г., 12:33:36 UTC+2 пользователь Tim Watson написал:
<br>> Hello all,
<br>>
<br>> It's been a busy week for Cloud Haskell and I wanted to share a few of
<br>> our news items with you all.
<br>>
<br>> Firstly, we have a new home page at <a href="http://haskell-distributed.github.com" target="_blank">http://haskell-distributed.<u></u>github.com</a>,
<br>> into which most of the documentation and wiki pages have been merged. Making
<br>> sassy looking websites is not really my bag, so I'm very grateful to the
<br>> various author's whose Creative Commons licensed designs and layouts made
<br>> it easy to put together. We've already had some pull requests to fix minor
<br>> problems on the site, so thanks very much to those who've contributed already!
<br>>
<br>> As well as the new site, you will find a few of us hanging out on the
<br>> #haskell-distributed channel on freenode. Please do come along and join in
<br>> the conversation.
<br>>
<br>> We also recently split up the distributed-process project into separate
<br>> git repositories, one for each component that makes up Cloud Haskell. This
<br>> was done partly for administrative purposes and partly because we're in the
<br>> process of setting up CI builds for all the projects.
<br>>
<br>> Finally, we've moved from Github's issue tracker to a hosted Jira/Bamboo setup
<br>> at <a href="https://cloud-haskell.atlassian.net" target="_blank">https://cloud-haskell.<u></u>atlassian.net</a> - pull requests are naturally still welcome
<br>> via Github! Although you can browse issues freely without logging in, you will
<br>> need to provide an email address and get an account in order to submit new ones.
<br>> If you have any difficulties logging in, please don't hesitate to contact me
<br>> directly, via this forum or the cloud-haskell-developers mailing list (on
<br>> google groups).
<br>>
<br>> As always, we'd be delighted to hear any feedback!
<br>>
<br>> Cheers,
<br>> Tim
<br>
<br></div></div></blockquote></div><div class="HOEnZb"><div class="h5">
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "parallel-haskell" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:parallel-haskell%2Bunsubscribe@googlegroups.com" target="_blank">parallel-haskell+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
<br>
<br>
</div></div></blockquote></div><br></div>