Re: Journal performance problems

[Pete Massiello <pmassiello@xxxxxxxxxxxxxxxx>]

You should have the Disk controller with the 104MB of write cache (or 
better if you have PCI-X towers/technology), if you have the older 
controllers it will slow writing the Journal Rcvrs.  I would also 
recommend adding another mirrored disk set to spread your I/O.

   Pete Massiello

oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx wrote:

> Hello,
>
> well, we are currently setting up our HA solution (DataMirror). 
> Therefore, we had to start journalling on all production files.
>
> The journals are located in ASP2, which has 1 (mirrored) disk drive with 
> about 17.5GB capacity (type 6718).
>
> We now find we have severe performance problems some times. There's an 
> invoicing job that normally runs about 1:30 hours and now takes 2:30 w/o 
> much change in database activity. The only other active batch job at that 
> time is also database intensive and runs longer than normally.
>
> My guess is these jobs are waiting for journal entries to be written. The 
> ASP2 disk drive is very busy at that time.
>
> Any ideas on how to confirm this?
>
> Also, we could add a disk drive to ASP2, which should help some. Or might 
> it be better to cancel ASP2 and add the disks to ASP1? 
>
> I've started Management Central performance monitoring to get a better 
> look at system activity.
>
> Any suggestions?
>
> Regards,
>
> Oliver
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> .
>
>