Possible performance problem in Magnolia 4.4

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.1.2
• Fix Version/s: None
• Component/s: None
• Labels:

  None
• Environment:

  Magnolia 4.4.4
  Stripes 1.5.6
  Stripes module 4.1.2

I still don't have all the details for the problem, but I start adding it just in case someone else have it with better informations.

The rendering of a single, jsp-based, magnolia page with a couple of paragraph takes more or less 100ms (machine depending, obviously), and a part of this time is spent traversing the filter chain. Now if you use Magnolia 4.4 and the stripes renderer, you'll see that each action added to the page will add a little less than 100ms to the page rendering, even if the action completely empty (doing nothing) and just forwards to a jsp. You won't notice it if there are just a couple of actions in page, but this will eventually become a problem when there is a dozen of actions involved. Obviously if you want to try it you should create a page with at least 10 empty actions, because with one or two the behavious is eaten by network time and statistics.

I don't know if this is due to the new Magnolia 4.4 dispatching, but seems something new, I didn't remember this behaviour. At a first glance seems that the time spent is for a new filter chain's traversal, but it's just a hypotesis.

• Assignee:

  Fabrizio Giustina

  Reporter:

  Danilo Ghirardelli

• Created:

  01/Jun/11 15:44

  Updated:

  01/Jun/11 15:44