caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
	Rich Neswold <rich.neswold@gmail.com>,
	"caml-list@yquem.inria.fr" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Smart ways to implement worker threads
Date: Sun, 18 Jul 2010 01:00:50 +0300	[thread overview]
Message-ID: <B25CDBD8-3D53-4B66-9099-813054E1DE23@gmail.com> (raw)
In-Reply-To: <87tynxc35v.fsf@frosties.localdomain>

It looks like the multi core architectures will be around for a while only to be superseded by more advanced parallel micro-architectures.

Of course computation-bound apps will benefit more but this does not mean that memory intensive apps will not run well on multi core architectures. Carefully optimized code will run great on multi core architectures with high memory bandwidth. Depending on the application of course.

Right now it seems to me that shared mem is more suitable for data mining apps (and many other including scientific computing apps). Data mining has never been embarrassingly parallel and it's difficult to get good speedup on distributed architectures. I should know I've worked on the parallel solution of two such problems. Provided that the space complexity is manageable, I think such network-bound cluster algorithms have more efficient counter-parts on multi-core. In data mining algos some data may have to be replicated or communicated. If the space doesn't blow up, NVIDIA Fermi would be ideal for those problems. No more copying. On the new Tesla max memory will be 6x4=24gb.

For all I care Intel is obsolete until they give me a thousand cores.

Shared memory support is essential at any rate. I don't see why we can't have it in an excellent way!

Best,

Eray


  reply	other threads:[~2010-07-17 22:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 16:09 Goswin von Brederlow
2010-07-15 15:58 ` [Caml-list] " Rich Neswold
2010-07-15 16:19   ` David McClain
2010-07-15 17:16   ` Ashish Agarwal
2010-07-15 18:24   ` Goswin von Brederlow
2010-07-15 18:37     ` David McClain
2010-07-15 18:40     ` David McClain
2010-07-15 19:56     ` Rich Neswold
2010-07-16  4:02       ` Goswin von Brederlow
2010-07-16  4:23         ` Rich Neswold
2010-07-16 13:02           ` Goswin von Brederlow
2010-07-16 14:40             ` Dawid Toton
2010-07-16 16:18             ` [Caml-list] " Rich Neswold
2010-07-17 17:53               ` Eray Ozkural
2010-07-20  4:54             ` Satoshi Ogasawara
2010-07-17 18:34         ` Eray Ozkural
2010-07-17 19:35           ` Goswin von Brederlow
2010-07-17 22:00             ` Eray Ozkural [this message]
2010-07-15 16:32 ` Romain Beauxis
2010-07-15 17:46   ` Goswin von Brederlow
2010-07-15 18:44     ` Romain Beauxis
2010-07-16  3:52       ` Goswin von Brederlow
2010-07-16  4:19         ` Romain Beauxis
2010-07-16 13:05           ` Goswin von Brederlow
2010-07-16 13:20             ` Romain Beauxis
2010-07-17  9:07               ` Goswin von Brederlow
2010-07-17 13:51                 ` Romain Beauxis
2010-07-17 14:08                   ` Goswin von Brederlow
2010-07-17  9:52 ` Goswin von Brederlow
2010-07-17 14:20   ` Romain Beauxis
2010-07-17 15:52     ` Goswin von Brederlow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B25CDBD8-3D53-4B66-9099-813054E1DE23@gmail.com \
    --to=examachine@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=goswin-v-b@web.de \
    --cc=rich.neswold@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).