Re: Debug slows program by a factor of 30?

Agreed.

The JNI interface creates a lot of overhead even without debug. And as Justin has noted, when Java is in the mix the debugger performance goes to hell in a handbasket. Not sure why and all of my nuts-and-bolts-of -the-debugger contacts have long retired.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Dec 5, 2017, at 12:38 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

Jon's advice is valid (I see that when my program manipulates a large DS), but in this particular case, I blame Java.


-----Original Message-----
From: Greg Wilburn [mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, December 05, 2017 9:14 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug slows program by a factor of 30?

That is some good information... but in this case, I had the monitor tab in focus with two variables.

A subject better suited for another forum, I was getting a message
"Space offset X'00000000' or X'000080004FB25000' is outside current limit for object OE.RW GWILBURN 833575."
When using WRTHTMLTOSTMF.

The really odd thing is that I added GetHtmlBytesBuffered to see if I was exceeding the allowable size, and the error ceased to occur.

Bottom line is that it took me nearly an hour to run the process.

Thanks for the good info!


--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.