[MAGNOLIA-2121] activation: use a thread per subscriber Created: 24/Apr/08  Updated: 23/Jan/13  Resolved: 15/May/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 3.6

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLACTIVATION-60 Refactoring of activation components ... Closed
relation
is related to MAGNOLIA-1603 Activating multiple inbox workitems (... Closed
is related to MAGNOLIA-2122 activation: save the packages in temp... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

All activation requests are executed synchronous. As the main processing is done on the subscriber we shouldn't do that. This could improve activation speed on multi instances installations a lot.

A simple implementation shouldn't be that difficult



 Comments   
Comment by Jan Haderka [ 15/May/08 ]

Done. From now on up to 10 subscribers will get content activated simultaneously. Not much point to try to activate even more in parallel since we would be hitting other bottlenecks.
WARNING: As part of solution synchronization blocks have been removed from activation (not much point running multiple threads when everything is synchronized anyway). I tried to do extra testing to make sure no content gets corrupted, but if we start seeing such on the occasion, removal of the synchronized block will be most likely the cause.

Generated at Mon Feb 12 03:33:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.