G
gus
Guest
No. the number of records you read is determined by how many there are and what queries your code executes, not by the size of the lock table. making the lock table larger consumes more memory (72'ish bytes per entry these days). that in itself is not detrimental unless you begin to incur paging I/O. reading the lock table via for each_lock will of course take longer but that is not a normal thing for an application to be doing.
Continue reading...
Continue reading...