usually I tried to follow the rules:
1. Keeping the primary group size (frame size) in balance with the
operating system IO operations. aix is normally performs the IO in 4KB
blocks, so trying to use the frames in the same size to get the group
on one go. in your example the F.LOCKING file has frame size 8KB so
for every READ/WRITE the system must do 2 IO operations because I
think jbase must read the whole logical block and then searching for
the record within the block.
2. Avoiding too many records per frame especially for the heavy used
tables even the records size is too small and can fit in the frame.
Before system reads/writes the record in the frame the whole frame is
locked for the integrity purposes that is released after the IO
operation is completed. During this moment all the records within the
particular frame are not available for other requests. And jbase call
must spend some time to locate the record position within too many
records in the frame. Then it's better to increase number of frames to
reduce the number of records per frame even you will have more free
space in the frames.
3. this is out of topic but the F.LOCKING is one of the most
frequently used file. In this file you have too many records (more
than usually) and I assume that majority of the records are out of
date or obsolete. sometimes the proper cleaning (also in other
important files) and then reducing the file size will help a lot. for
the second file EB.CONTRACT.BALANCES I don't see a reason to resize it
to increase the number of frames because the physical size of the file
is more than 1GB, but the data are about 400MB only, so a lot of free
space.
4. and there are many other possibilities.



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

Reply via email to