addTraceStatement() and Performance

[Sir Rawlins]

Hello Guys,

I wanted to get some feedback on your experience of addTraceStatement
() and the impact it has on performance within an app. I've recently
been working on a project whereby I had a couple of pages within the
application which were running exceedingly slowly, I mean, we're
talking 30 - 40 seconds to load an array of maybe 40 objects.

I tracked this performance issue down to an addTraceStatement() that
was tracing the array of objects which were being returned and placed
into the event. As soon as I remove the trace statement execution on
the page fell to around 300ms. This performance impact was present
even when the application was not in debug mode.

I've done a little testing and found that any time I'm placing arrays
of objects into the trace it has a huge impact on performance.

What's the reasoning behind this? is perhaps the cfdump being rendered
even if debug is false?

I thought I'd get a little more feedback from you before logging this
in the bugs list.

Cheers all,

Rob

[Chris Blackwell]

The performance hit is down to addTraceStatement() performing a cfdump on any complex objects. 

This was discussed on the list a month or so back

http://groups.google.com/group/model-glue/browse_frm/thread/d59bbf06b8dc0478

in the short term you can hack your addTraceStatement method as i suggested to return immedeately if debugging is off which will avoid the cfdump.

and hopefully shortly the logging in MG will get revisited and this and the other issues will be sorted.

Cheers, Chris

2010/1/13 Sir Rawlins <robert....@thinkbluemedia.co.uk>

--
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog

You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to model...@googlegroups.com
To unsubscribe from this group, send email to
model-glue+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en

[Sir Rawlins]

Thanks Chris,

I suspected that to be the case, thanks for letting me know, I'm glad
that it's in the pipe-line to be addressed.

Rob

On 13 Jan, 12:33, Chris Blackwell <ch...@team193.com> wrote:
> The performance hit is down to addTraceStatement() performing a cfdump on
> any complex objects.

> This was discussed on the list a month or so backhttp://groups.google.com/group/model-glue/browse_frm/thread/d59bbf06b...

>
> in the short term you can hack your addTraceStatement method as i suggested
> to return immedeately if debugging is off which will avoid the cfdump.
> and hopefully shortly the logging in MG will get revisited and this and the
> other issues will be sorted.
>
> Cheers, Chris

> <http://groups.google.com/group/model-glue/browse_frm/thread/d59bbf06b...>
>
> 2010/1/13 Sir Rawlins <robert.rawl...@thinkbluemedia.co.uk>

> > model-glue+...@googlegroups.com<model-glue%2Bunsubscribe@googlegrou ps.com>

[Zac Spitzer]

ahhh, the penny just dropped on why i have seen some really horrible
grinding i have seen whilst developing with mg...

2010/1/13 Sir Rawlins <robert....@thinkbluemedia.co.uk>:

--
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168

[Dan Wilson]

Yep. It is on the list to be sorted.


DW

“Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew.”

Guillaume Apollinaire quotes

[Chuck Savage]

I tested this too, I was wondering why things were so slow with MG and figured it was because I was still in development.  I patched the file and posted it in that thread Chris linked, and saw at least a 90% improvement!
--
Chuck Savage
http://SeaRisen.com