Re: Récapitulatif destiné à disruptor-net@googlegroups.com - 1 message dans 1 sujet

[Jimit Ndiaye]

Is it worth adding a version that targets the IO thread pool for long running tasks?

Sent from my iPhone

On 23 Dec 2011, at 18:48, "disrup...@googlegroups.com" <disrup...@googlegroups.com> wrote:

  Récapitulatif des sujets du jour

Groupe: http://groups.google.com/group/disruptor-net/topics

• RoundRobinThreadAffinedTaskScheduler [1 mise à jour]

 RoundRobinThreadAffinedTaskScheduler

Olivier <ma...@odeheurles.com> Dec 23 04:20AM -0800  

I've check-in a TaskScheduler which contains a thread pool and pin
each thread to a core: RoundRobinThreadAffinedTaskScheduler.
 
The Disruptor constructor takes a TaskScheduler used to run the event
processors.
 
You will find examples in the performance tests: each disruptor perf
test now has 2 versions: one with affinity and another one without.
 
Details of the commit on github:
https://github.com/odeheurles/Disruptor-net/commit/6e3aad51722064575896cce445c688a7b58381d8
 
Olivier


 

Vous avez reçu ce message, car vous êtes abonné au groupe Google disruptor-net.
Vous pouvez l'envoyer par e-mail.
Pour résilier votre abonnement à ce groupe, envoyez un message vide.
Pour accéder à d'autres options, visitez ce groupe.

[Olivier]

Events processors generaly run for the full lifetime of the application so this task scheduler does not rely on the .net thread pool: it has it's own internal pool of threads.

Do you see a usecase where it would be better to use the normal thread pool?

Olivier