Re: JVM CPU queueing -- MIDRANGE-L

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

Subject: Re: JVM CPU queueing
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Wed, 22 Oct 2014 13:53:22 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Oct 22, 2014 at 1:38 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

Each and every task has to wait 1
second, and then do the loop.

If the wait were inside the loop, [....]

I was careless in my word choice. I should have said "sleep" instead
of "wait" in both cases above.

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: JVM CPU queueing , Nathan Andelin

This mailing list archive is Copyright 1997-2025 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.