From: Shivkumar Chandrasekaran <shiv@ece.ucsb.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] native threads not parallel?
Date: Thu, 20 Feb 2003 15:10:35 -0800 [thread overview]
Message-ID: <847A10BA-4528-11D7-8C93-000393942C76@ece.ucsb.edu> (raw)
Not sure if this issue from an earlier discussion was fully resolved or
not. But I seem to have the same problem as discussed by Markus Mottl
(see attachment below) on Mac OS X 10.2.4 on a dual processor G4
machine. An earlier message in that thread mentioned that there was no
such problem on dual-processor Linux machines.
I have two questions:
1. Has anybody else figured out how to get parallelism using native
threads on Mac OS X?
2. Will I get the parallelism if I switch to LinuxPPC?
Thanks,
--shiv--
PS: Does ocaml work properly on LinuxPPC?
> Re: [Caml-list] native threads not parallel?
> To :Xavier Leroy < Xavier.Leroy@inria.fr >
> Subject :Re: [Caml-list] native threads not parallel?
> From :Markus Mottl < mottl@miss.wu-wien.ac.at >
> Date: Thu, 21 Jun 2001 15:43:16 +0200
> Cc: OCAML < caml-list@inria.fr >
> Content-Disposition: inline
> In-Reply-To: < 20010615233325.B24915@miss.wu-wien.ac.at >; from
> mottl@miss.wu-wien.ac.at on Fri, Jun 15, 2001 at 23:33:26 +0200
> References: < 20010615184931.A25835@miss.wu-wien.ac.at > <
> 20010615191046.A20258@pauillac.inria.fr > <
> 20010615204218.C25835@miss.wu-wien.ac.at > <
> 20010615233325.B24915@miss.wu-wien.ac.at >
> User-Agent: Mutt/1.2.5i
> On Fri, 15 Jun 2001, Markus Mottl wrote:
> > I have just been told that things work smoothly with dual-processor
> > machines under Linux, and it also turned out due to more
> experimentation
> > that the behaviour of native threads under Solaris is comparable to
> > a lottery: when running very long, it seems that multiple threads are
> > used. Sometimes. But sometimes you can also get bus errors. It's
> really
> > unpredictable. Better don't bother with native threads under
> Solaris...
>
> I couldn't resist and have done another test now. First, I have made
> sure that multiple threads work under C. As Xavier has pointed out,
> this
> requires setting the concurrency level to more than the default of 1.
> Works fine (= in parallel).
>
> Then I have written a small test program that tries to do the same
> under
> OCaml - but no success...
>
> Here are the the timings achieved by calling C via OCaml:
>
> Running sequentially:
> Wall clock time: 6.598713
>
> Running in parallel:
> Wall clock time: 6.601169
>
>
> Here are the the timings achieved by using C only (clearly runs faster
> with threads):
>
> Running sequentially
> Wall clock time: 6.995337
>
> Running in parallel
> Wall clock time: 3.910411
>
> The only thing I can imagine is that OCaml somehow changes
> scheduling so that the threads cannot run in parallel anymore, even if
> "enter_blocking_section" is used. Is this possible? Or am I just making
> some stupid mistake?
>
> Regards,
> Markus Mottl
--shiv--
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-02-20 23:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 23:10 Shivkumar Chandrasekaran [this message]
2003-02-21 0:15 ` Jacques Garrigue
2003-02-21 4:24 ` shivkumar chandrasekaran
2003-02-21 10:43 ` Markus Mottl
2003-02-21 15:11 ` Jacques Garrigue
2003-02-21 17:57 ` Markus Mottl
2003-02-24 17:39 ` Shivkumar Chandrasekaran
2003-02-21 0:32 ` Chris Uzdavinis
2003-02-21 1:56 ` james woodyatt
2003-02-21 4:43 ` shivkumar chandrasekaran
-- strict thread matches above, loose matches on Subject: below --
2001-06-15 16:49 Markus Mottl
2001-06-15 17:10 ` Xavier Leroy
2001-06-15 18:42 ` Markus Mottl
2001-06-15 21:33 ` Markus Mottl
2001-06-21 13:43 ` Markus Mottl
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=847A10BA-4528-11D7-8C93-000393942C76@ece.ucsb.edu \
--to=shiv@ece.ucsb.edu \
--cc=caml-list@inria.fr \
/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