[MGNLPN-209] Improve performance of personalization specific workspace wide observers Created: 07/May/15  Updated: 27/Aug/15  Resolved: 25/Aug/15

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.2, 1.1.3, 1.2.2

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 2h 25m
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPN-13 Create registry for all segments and ... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Sprint 7 (Kromeriz)
Story Points: 8

 Description   

Populating the variants registry takes several minutes at large repositories. This is being performed each and every time from scratch, e.g. it prolongs every server startup significantly.



 Comments   
Comment by Adrian Andermatt [ 12/May/15 ]

Hi Guys

Since this fix is quite important for our customer UZH I'd like to know with which version it will be fixed.

Thanks and regards,

Adrian

Comment by Zdenek Skodik [ 12/May/15 ]

Hi Adrian,

it's a candidate for 5.3.10.

Regards.

Comment by Christian Schroeder [ 20/May/15 ]

Hello,

can Magnolia please provide us a workaround for this problem? We tried to uninstall personalization, but there are several configurations which are needed to be done. So we need either a workaround or hotfix for this specific problem or bootstrap files which allow us to uninstall the personalization modules safely.

Our customer rates this issue critical.

Regards

Christian

Comment by Christian Schroeder [ 20/May/15 ]

Further explanation: If the modules are removed from Config Repository, they are installed again from ConfigLoader (which finds them in classpath I guess). So to uninstall we need to exclude those modules in pom before we amend the configs. And furthermore to the script Lars gave us, we need to be sure, that each class from those Modules, which is used in configuration (e.g. /modules/pages/apps/pages/subApps/detail@subAppClass) is changed to the corresponding class without personalization.

Can you please provide us with groovy script or even better with a PersonalizationUninstallTask ?

Best Regards

Christian

Comment by Lars Fischer [ 09/Jul/15 ]

The script has already been provided to Namics around May 20th. In the meantime, they were able to create the workaround for this problem.

Comment by Roman Kovařík [ 25/Aug/15 ]

The segment registry uses query to populate registries but the variant registry doesn't.

Generated at Mon Feb 12 06:35:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.