Re: Timeslice recommendations -- 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: Timeslice recommendations
From: Pete Hall <pbhall@xxxxxxxxxx>
Date: Fri, 08 Feb 2002 19:05:31 -0600
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

At 13:29 02/08/2002, Jay Peasley wrote:

>Obviously they aren't as big as hitters as QINTER and QBATCH. Has anyone
>played with these classes and have any recommendations?

Not specifically, but a few years ago I was in charge of tuning a new (at
that time) S30. I changed all the time slices to 1/10th of their shipped
value, and everything worked just fine. Interactive response improved a lot
too.

Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall/

As an Amazon Associate we earn from qualifying purchases.

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.