P
Piotr Ryszkiewicz
Guest
George, You are quite close... there is one field which takes about 1/4 of record size - if I compare RECORD-LENGTH of the record with LENGTH of that field. Why it's important ? And how did you know that ? In production I was going to set create limit to 300 and toss limit to 400. Create limit was 100 only during load - because during load records are created in one step and will never be updated. I am just running test with this setup, but it takes some time. If I increase toss limit to 500 as you suggested I will have shorter RM chain, but also worse space utilization... it would require another testing to say what's better. RECORD-LENGTH of template record is 236. This was very good question... as it made me think about that. That means, that during normal production when newly created record is allocated it takes at least 236 bytes, even if it's not filled yet, right ? If average record size is around 400, that means it will afterwards grow by around 170 bytes. That means create limit should be at least 170, am I right ? Regards, Piotr
Continue reading...
Continue reading...