× 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: Commitment Control Overhead
  • From: John Earl <johnearl@xxxxxxxxxx>
  • Date: Tue, 10 Mar 1998 21:58:15 -0800



Al Barsa, Jr. wrote:

> At 04:56 PM 3/9/98 -0600, you wrote:
> >Can someone steer me in the direction of statistics about using Commitment
> Control.  I have only found the Advanced Backup and Recovery text talking
> about CC, so far.

<snip>

> First of all, commitment control requires journaling.  The overhead of
> journaling is about 5%, assuming the journal receiver is in a separate ASP
> that has not overflowed.  The new 'remote journaling' support in V4R2 is
> about 14%.

5% ?? Wow! I'm surprised it's so high.  Would that be 5% of CPU usage or 5% of
average I/O time attributted to a job?

I would have expected that journalling with commitment control to a separate ASP
(where your head movement is going to be next to nil) would be almost
imperceptable.  Do many people see this large an impact?

jte

--
John Earl Lighthouse Software Inc.
8514 71st NW Gig Harbor, WA 98335
253-858-7388 johnearl@lns400.com

Without Lighthouse Network Security/400, your AS/400 is wide open.
--


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.