Hi,
We're using SmartGWT 4.0 and we're running a profiler to see if we can improve any performance bottlenecks. We notice in the profiler, calls to isc__debug__getStackTrace()--which take up a relatively large amount of time--sometimes 50ms.
We have not inherited any of the debug modules within our *.gwt.xml file. Are stack traces turned on by default and if so, is there any way to disable them?
I've looked through the FAQ, granted I may have overlooked something. Any advice is appreciated.
Thanks,
Jason
We're using SmartGWT 4.0 and we're running a profiler to see if we can improve any performance bottlenecks. We notice in the profiler, calls to isc__debug__getStackTrace()--which take up a relatively large amount of time--sometimes 50ms.
We have not inherited any of the debug modules within our *.gwt.xml file. Are stack traces turned on by default and if so, is there any way to disable them?
I've looked through the FAQ, granted I may have overlooked something. Any advice is appreciated.
Thanks,
Jason