Ridiculously slow performance -- are there tuning recommendations?

[PeteS]

Using the free trial of FusionDebug with a purchase in the works once my client does the paperwork. I have succeeded in getting remote debugging to work -- CF9 running on Linux (in a vm), FD running on my Windows 7 machine as part of Eclipse.

Connectivity works, and I get can FD to stop at breakpoints. The problem I'm having is that its performance is unacceptably slow -- it doesn't even connect for over a minute; stepping through lines of ColdFusion code can take 60-90 seconds per line, though some statements go as quickly as 4-5 seconds. My application runs with acceptable speed ordinarily; it's in the debugger that everything grinds to a productivity-sapping halt.

I manually edited the server's jvm.config per the FD instructions. Are there other tuning steps to take? It's hard to believe the product normally runs this slowly; I figure something on my end has to be misconfigured or could be configured better.

Any pointers?

Thanks,

-- Peter

[David Stockton]

Hello Peter,

There's two typical reasons...

1) Memory is very tight (almost exhausted) in Eclipse or CF - you can check this in CF with our FusionReactor tool (10day free trial is available on our website if you don't own a license)

2) The connectivity between FD and the CF9 machine is poor. The JDWP protocol

Other considerations are the version of Eclipse being used and the Eclipse View (eg CFEclipse) - if you find neither of the above hints help, please provide this information when you respond.

Best regards,

David Stockton

Fusion Teanm

--
You received this message because you are subscribed to the Google Groups "FusionDebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fusiondebug...@googlegroups.com.
To post to this group, send email to fusio...@googlegroups.com.
Visit this group at http://groups.google.com/group/fusiondebug?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Charlie Arehart]

And to add to what David said, and in response to your last comment (“It's hard to believe the product normally runs this slowly”), it really does not. Indeed, many are stunned at the speed, where one can use the step over command/key and see lines fly by as fast as one would see just holding the down arrow in the editor.

So I think you’re right with your follow-up point, “I figure something on my end has to be misconfigured or could be configured better.” Here’s hoping one of David’s suggestions helps you out.

And as for viewing the memory in Eclipse (in case that’s the problem), turn on “Show heap status" under Window > Preferences > General. You may also want to watch the Progress view (Window>Show View) to see if it shows anything amiss when things are slow.

Hope that helps.

/charlie