We're updating the issue view to help you get more done. 

Optimize concurrency for DefaultPipelineRegistry

Description

Simple solution for 2.0:

  • Dictionary + lock-statement in DefaultPipelineRegistry should be replaced by ConcurrentDictionary.

  • current implementation contains two fields, those must be unified to a single field, otherwise we have race conditions.

  • The DefaultPipeline can be accessed without a lock statement.

  • Access to the registered pipelines via IPipelineRegistry.Get(...) still requires a lock-statement for concurrency reasons.

Advanced solution for 3.0: See

Assignee

Michael Ketting

Reporter

Michael Ketting

Labels

None

Time tracking

0m

Components

Fix versions

Affects versions

Priority

Normal
Configure