[MAGNOLIA-2879] low performance on activate this node Created: 02/Oct/09 Updated: 23/Jan/13 Resolved: 08/Oct/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.6.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Andrea Castelli | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | activation, jackrabbit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Visible to: |
Marco Induni, Matteo Pelucco
|
| Description |
|
I wrote this post on magnolia user by I received no answer. My question is related with the others of Marco Induni. I'm developing on Magnolia 3.6 and I registered low performance when users click on "activate this page" (without subpages). My question is: what does it happen when a user clicks on activate this page whitout subpages? I think that an XML is made and trasferred to the public nodes. I think this is similar to activate a leaf. But the behaviour noticed tell me that I'm wrong. Maybe does Jackrabbit lock the nodes under the page activated? Thank you. |
| Comments |
| Comment by Andrea Castelli [ 06/Oct/09 ] |
|
Fixed. I disabled versioning from admin tree. The answers of Jan Haderka on the mailing list were very helpful. |
| Comment by Philipp Bärfuss [ 08/Oct/09 ] |
|
As far I understand this is not an issue anymore. |