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



On Tue, Sep 20, 2011 at 9:23 AM, <rob@xxxxxxxxx> wrote:
Honestly, there are some performance concerns with journalling.  We ended
up purchasing IBM's
Resource
  ID     Option  Feature  Description
5770SS1   42       5117    HA Journal Performance

That significantly helped our month end's.  Much more so than SSD's did.


More correctly, there are performance concerns of journalling without
using commitment control that can be solved by the above license
program option.

If using commitment control, the above will have no effect. The above
allows the system to cache journal entries for writes done outside of
commitment control. The caching behavior is automatic when you use
commitment control.

However, in order to benefit from caching if you are using commitment
control, you need to make sure your transactions are large enough.
Committing after every write isn't going to benefit from the cache.
Ideally, you'd want as close to 128KB of journal entries generated
before the commit. I tend to simply commit blocks of 1000 records.

HTH,
Charles

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.