caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Romain Beauxis <toots@rastageeks.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Smart ways to implement worker threads
Date: Thu, 15 Jul 2010 19:46:53 +0200	[thread overview]
Message-ID: <874og0hc36.fsf@frosties.localdomain> (raw)
In-Reply-To: <201007151132.07821.toots@rastageeks.org> (Romain Beauxis's message of "Thu, 15 Jul 2010 11:32:07 -0500")

Romain Beauxis <toots@rastageeks.org> writes:

> 	Hi !
>
> Le mercredi 14 juillet 2010 11:09:49, Goswin von Brederlow a écrit :
>> What do you think? Other Ideas? Ready-to-use modules for this?
>
> I won't commend on CML; which I don't know at all but the description you give 
> seems to match the requirements we had in liquidsoap when we implemented out 
> internal scheduler.
>
> The module that implements it is there:
>   http://www.rastageeks.org/ocaml-duppy/Duppy.html
>
> Basically, it provides a facility around to create a select-based scheduler 
> where you can define your custom priorities, create a queue for a certain range 
> of priority and run them in threads.
>
> The main scheduling is done by inside the tasks, so this is transparent.
>
> Basically, to use it, you initiate a scheduler, create threads running 
> associated queues and submit tasks to the scheduler.
>
>
> Romain

I don't see where that helps at all. I don't want to offload the IO into
threads and schedule them and Duppy seems to only handle IO tasks.

Except if I pick Solution 1 and then it still doesn't help anything
since I can already run select in every thread. The IO should not be
scheduled by priorities and isn't the bottleneck anyway. Seems this
would just add overhead.

MfG
        Goswin


  reply	other threads:[~2010-07-15 17:46 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
2010-07-15 16:32 ` Romain Beauxis
2010-07-15 17:46   ` Goswin von Brederlow [this message]
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=874og0hc36.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=caml-list@yquem.inria.fr \
    --cc=toots@rastageeks.org \
    /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).