G
George Potemkin
Guest
By the way, we can use the similar idea for the sequences. Set a sequence increment, let's say, to 100. So when Progress session asks for the next sequence value it can use the range of values either to create 100 new records in one transaction or just to keep them as a pool of the values for a future use. Such approach will significantly reduce the number of requests to the sequence block and will increase the performance in the cases when the sequences are actively used to create the records in the different tables. Unfortunately it will not help much if the concurrent sessions are creating the records in the same table because the access to a data block at the head of RM chain will stay a bottleneck (of the same "insalubrity" as the access to the sequence block was).
Continue reading...
Continue reading...