× 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.



Nigel,
Thanks for the tip. I changed it and it originally took about 260% of the
CPU. I ran the CRTJVAPGM command again and it took around 10 again.

I appreciate the help from everyone on this. I don't really have a need yet
for it, so I have time to play with it and attempt to have it run a little
better.

I think I need to look at the whole thing again anyway. I just ran it on my
PC and it was taking about 50% of the CPU.

Looks like it's time for me to start learning how to optimize Java.

Thanks to all,
--
James R. Perkins

On Fri, Aug 22, 2008 at 3:33 AM, <NGay@xxxxxxxxxxxxx> wrote:

James,

Aha, and there it is:
while (!false);

That's what's eating up all your CPU. The Timer runs creates its own
thread so there's no need to keep the thread that your main () method is
running in alive. You then need to change your
timer_ = new Timer (true);
to
timer_ = new Timer (false);

With this param as "true", the Timer thread WILL end as soon as the main ()
thread ends.

Hope this helps,

Nigel Gay.


--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.