Can anyone suggest some tools to help us find the cause of a slowdown in
part of our Lucee application? What are some common tools for this? I’m
guessing there are some Java profiling tools, but we haven’t used any in
the past. Thanks for the suggestions!
You can try fusion reactor…
GertSent from somewhere on the road
Am 11.05.2015 um 16:37 schrieb Jonathan Brookins <@Jonathan_Brookins>:
Can anyone suggest some tools to help us find the cause of a slowdown in part of our Lucee application? What are some common tools for this? I’m guessing there are some Java profiling tools, but we haven’t used any in the past. Thanks for the suggestions!
You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1c0600b0-8214-44b2-a10e-ddf39baa29b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I’ve looked at the debugger in the past, but the problem I had was
suppressing it for ajax scripts. It’s probably possible, but I ran out of
time to investigate it. I’ll try it again, thanks for the suggestion.On Monday, May 11, 2015 at 11:11:38 AM UTC-4, upfron...@gmail.com wrote:
Have you tried the built-in debugger? (Just turn it on in the Lucee
admin) It will tell you how long each resource is taking to build a page
and how long each query takes, etc.On Monday, May 11, 2015 at 10:37:22 AM UTC-4, Jonathan Brookins wrote:
Can anyone suggest some tools to help us find the cause of a slowdown in
part of our Lucee application? What are some common tools for this? I’m
guessing there are some Java profiling tools, but we haven’t used any in
the past. Thanks for the suggestions!
on pages that are processed by others (including machines a-la ajax
etc.) simply add:
<cfsetting showdebugoutput="#false#">
Igal Sapir
Lucee Core Developer
Lucee.org http://lucee.org/On 5/11/2015 8:43 AM, Jonathan Brookins wrote:
I’ve looked at the debugger in the past, but the problem I had was
suppressing it for ajax scripts. It’s probably possible, but I ran
out of time to investigate it. I’ll try it again, thanks for the
suggestion.On Monday, May 11, 2015 at 11:11:38 AM UTC-4, upfron...@gmail.com wrote:
Have you tried the built-in debugger? (Just turn it on in the Lucee admin) It will tell you how long each resource is taking to build a page and how long each query takes, etc. On Monday, May 11, 2015 at 10:37:22 AM UTC-4, Jonathan Brookins wrote: Can anyone suggest some tools to help us find the cause of a slowdown in part of our Lucee application? What are some common tools for this? I'm guessing there are some Java profiling tools, but we haven't used any in the past. Thanks for the suggestions!–
You received this message because you are subscribed to the Google
Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to lucee+unsubscribe@googlegroups.com
mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com
mailto:lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/2e6f82d3-277e-456b-8dc3-2b4a880e1053%40googlegroups.com
https://groups.google.com/d/msgid/lucee/2e6f82d3-277e-456b-8dc3-2b4a880e1053%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.
keep in mind that the CGI.SCRIPT_NAME will start with a ‘/’ so the
example test below would not work “out of the box”.On 5/11/2015 8:52 AM, Igal @ Lucee.org wrote:
well, if those pages are identifiable in any way then you can simply
add it to Application.cfc in onRequestEnd()something like:
/** Application.cfc*/
component {function onRequestEnd(target) { if ( left(CGI.SCRIPT_NAME, 4) == "ajax" ) setting showdebugoutput=false; }}
Igal Sapir
Lucee Core Developer
Lucee.org http://lucee.org/On 5/11/2015 8:49 AM, Jonathan Brookins wrote:
Thanks, Igal, but I had hoped to find a solution that didn’t require
finding all of the ajax templates and add a cfsetting to them. If
that is the only way I can do it when I get some time.On Monday, May 11, 2015 at 11:45:41 AM UTC-4, Igal wrote:
on pages that are processed by others (including machines a-la ajax etc.) simply add: <cfsetting showdebugoutput="#false#"> Igal Sapir Lucee Core Developer Lucee.org <http://lucee.org/> On 5/11/2015 8:43 AM, Jonathan Brookins wrote:I've looked at the debugger in the past, but the problem I had was suppressing it for ajax scripts. It's probably possible, but I ran out of time to investigate it. I'll try it again, thanks for the suggestion. On Monday, May 11, 2015 at 11:11:38 AM UTC-4, upfron...@gmail.com wrote: Have you tried the built-in debugger? (Just turn it on in the Lucee admin) It will tell you how long each resource is taking to build a page and how long each query takes, etc. On Monday, May 11, 2015 at 10:37:22 AM UTC-4, Jonathan Brookins wrote: Can anyone suggest some tools to help us find the cause of a slowdown in part of our Lucee application? What are some common tools for this? I'm guessing there are some Java profiling tools, but we haven't used any in the past. Thanks for the suggestions! -- You received this message because you are subscribed to the Google Groups "Lucee" group. To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com <javascript:>. To post to this group, send email to lu...@googlegroups.com <javascript:>. To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/2e6f82d3-277e-456b-8dc3-2b4a880e1053%40googlegroups.com <https://groups.google.com/d/msgid/lucee/2e6f82d3-277e-456b-8dc3-2b4a880e1053%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.–
You received this message because you are subscribed to the Google
Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to lucee+unsubscribe@googlegroups.com
mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com
mailto:lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/e9a2f8c8-63e6-4be7-8c20-a1ee96c31ddb%40googlegroups.com
https://groups.google.com/d/msgid/lucee/e9a2f8c8-63e6-4be7-8c20-a1ee96c31ddb%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.
Have you tried the built-in debugger? (Just turn it on in the Lucee admin)
It will tell you how long each resource is taking to build a page and how
long each query takes, etc.On Monday, May 11, 2015 at 10:37:22 AM UTC-4, Jonathan Brookins wrote:
Can anyone suggest some tools to help us find the cause of a slowdown in
part of our Lucee application? What are some common tools for this? I’m
guessing there are some Java profiling tools, but we haven’t used any in
the past. Thanks for the suggestions!
Check for cgi.http_x_requested_with. This should only have a value (like “xmlhttprequest”)
for AJAX requests.On Monday, May 11, 2015 at 3:10:46 PM UTC-4, Gert Franz wrote:
You can as well check, wether the request type is a xsr request (I don’t
know that from the top of my head, but it refers to any Ajax call). Then
you will even be able to turn off debugging for scripts that do not contain
the label Ajax.In addition remember that even if you turn off the debugging output, in
the admin you will still be able to check the debugging output.Gert
Sent from somewhere on the road