Andre, I'm with Rick. He suggested "new partfile". But maybe some kind of queue or workfile, that routinely gets flushed, merging to modulo 1. And maybe zero length record or very small, so that 250 ids all land in the same group? Is group size 4KB?
What does that have to do with the lock table in memory, you (or some lurker) may ask? When a record is locked, UV uses the inode & group# to determine where to plant the lock in the lock table. So that means that all these records will be assigned to the same lock group, since inode & group# (i.e., 1) will be the same for all. If you gave it a larger minimum.modulus, or converted that queue/work file to static, then, when you lock many or all records at once, that would spread the load across several lock groups, since the inode&group# combo would vary from record to record. cds P.S. I *think* splits and merges are suspended on groups that have records currently in the lock table. (Since group# determines where something is in the lock table, you couldn't have that being changed out from under you.) So as long as a record remains locked, your dynamic file will be not quite so dynamic. You might be hitting that, too. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
