× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mike,

Wow, it appears have the view "ERROR LOG" view open really slows down the parser. Close it, and lighten fast response from LPEX! <Awesome!>

I guess it is sort like the view "Variables" in debug mode, do NOT have it open, unless you actually using it. Or at least not in focus.

But, just having the "Error Log" view open, slows down the parser, even if it is NOT in focus.

Only open the view "ERROR LOG", if you want to see what it is doing in back-ground. Be aware, it will slow down the LPEX editor.

I now LOVE RDI 9.6 AGAIN! Thanks for this valuable tip Mike!


-Ken Killian-


-----Original Message-----


My guess is that your PC is just really really busy, unrelated to the test-fix changes.

If you have the Error Log view open and the high detail logging enabled then as the workspace Error Log grows it will take more and more CPU to process the logging events. Add to that doing several big actions quick together (all adding more events) the load will bring things to a standstill making it appear that RDI is unresponsive. My quick suggestion would be to close the Error Log view unless you actually are looking at the .log.

Mike

Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support IBM Canada Ltd. Laboratory


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.