The most likely cause of performance problems is incorrect or
inefficient program logic. Please provide sample code to recreate
the problem if you wish help with that type of problem.
If running a program with a lot of say or trace output, you can
limit negative impact on the jEdit UI thread by not using the option
to "Run compiled classes in jEdit" (assuming the program does not
access any jEdit APIs).
-- Kermit
On 12/18/2012 5:41 AM, Kenneth Klein
(TEMA TPC) wrote:
I am running a
netrexx program that is maxing out one of my 4 processors
and creeping along at a crawl and causing jedit to perform
slowly as well.
Granted it has
a couple of tight nested loops, and lots of say commands and
I’m tracing, but this is really bad.
Ken K.
_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/
_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive :
http://ibm-netrexx.215625.n3.nabble.com/