On Feb 11, 2011, at 12:36 PM, Nils Breunese wrote:

> 
> Grégory Joseph wrote:
> 
>> Somehow this sounds familiar, but I can pinpoint on the top of my head 
>> where/when I saw that in the past. It's definitely not wanted... which 
>> version are you using ?
> 
> This is on Magnolia 4.3.8 (EE, STK/ETK 1.3.5). If you put a breakpoint in a 
> paragraph model class, do you only hit it once per page instance?
NO, you hit it once per paragraph instance. Using same paragraph multiple times 
on the page results in multiple executions of the paragraph model.
Other thing to check for is paragraph definitions similar to the one in 
question or w/o need for own model that might have been copied and retained 
reference to the model class in question.

HTH,
Jan

> 
> Nils.
> 
>> On 11 Feb 2011, at 11:36, Nils Breunese wrote:
>> 
>>> Hello,
>>> 
>>> While debugging a performance issue with our code we noticed that 
>>> paragraphs get executed two and sometimes three times. This is on a 
>>> Magnolia author instance in development mode. We tried making sense of the 
>>> call stack, but it's pretty huge, so I figured we might just ask first. Is 
>>> this normal and/or expected? Does this also happen on public instances or 
>>> non-development instances? Or is this unexpected and something we need to 
>>> investigate further ourselves?
>>> 
>>> Nils.
> 
> ------------------------------------------------------------------------
> VPRO   www.vpro.nl
> ------------------------------------------------------------------------
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to