Project

General

Profile

Feature #2282

make number of pattern engine instances per conversion profile configurable

Added by Eric Faulhaber almost 10 years ago. Updated over 7 years ago.

Status:
Hold
Priority:
Normal
Assignee:
-
Start date:
04/11/2014
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD

Related issues

Related to Database - Feature #2276: create a work queue of PatternEngine instances for runtime conversion tasks Closed

History

#1 Updated by Eric Faulhaber almost 10 years ago

  • Status changed from New to Hold
  • Target version changed from 23 to Milestone 17

Currently, we create one pattern engine instance per conversion profile (e.g., schema/p2o, annotations/annotations, etc.). All runtime conversion operations across all sessions have to be handled by these single instances, which operate as critical sections (e.g., one session has access at a time, until it is finished). Once each profile has its rule-set expressions compiled, they are very fast to execute (around 1-2ms. on an i7 laptop), so I don't expect this to cause a bottleneck. If, however, this proves to be a problem in performance/scalability testing, we could add configuration to the directory to specify the number of pattern engines to create, by profile.

Each such instance has a significant memory footprint, since compiled expressions are not shared across pattern engine instances.

#2 Updated by Greg Shah over 7 years ago

  • Target version changed from Milestone 17 to Performance and Scalability Improvements

Also available in: Atom PDF