Jim wrote: > You can try to improve the performance by: > > 1) Defragmenting the jBASE files by jrf'ing them, or if they are being > resized too big (which seems to be the case lately), then writing a > script to dd them to new copies then moving them back over the original, > using a large block size with dd (to give a large chance that the > filesystem will allocate contiguous disk).
Ben> before I run COB, I refresh the environment. So i think we don't have this problem. > 2) Make sure the files are sized correctly of course; > 3) Take in to account the fact that there is probably transaction > journaling going on; Ben> I check the account and customer.account table. They are set to use LOG. when I run jlogstatus to check, it reports we don't have the license to run in our benchmark server. it means we don't use the jbase transaction journal. right? In production, they are using transaction journal. the transaction journal log file is using separater LV and PV. > 4) Ask for advice from TEMENOS and the SAN supplier on tuning the SAN > for jBASE access patterns; > First though, make your benchmarks with a local array, to give you a > base point for comparison. Then make one change at a time and re-run the > benchmarks. Ben> I have tested it. if I use the file system in rootvg. the throughput is only 20MB/s. If using SAN, I can get the 400MB/s (random write) using the disk IO simulation tool. > Ben> This weekend, we will run benchmark mark again. God bless us. :) > Jim --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
