Max Locks Forever

How would one find out the "maximum number of locks in use" for a period. lockreqs from onstat -p does me no good. I have a system that is stressed for memory and I'm running 100000 locks. They probably could do ok with less. This is 9.40.TC2 on Windows sending to informix-list

each lock is 43.2 bytes so that will be 4.11 Mb Are you really that stressed on memory?

<david@smooth1.co.uk> schrieb im Newsbeitrag news:1124322017.796622.266870@o13g2000cwo.googlegroups.com... > > each lock is 43.2 bytes so that will be 4.11 Mb huh? 43.2 bytes? 43 bytes plus 0.2 bytes? 43 bytes plus 1.6 bits? is this a quantum computing newsgroup? Or is 43.2 an average value for a lock? Can you please tell me where that information comes from? Sorry for being stupid Dirk -- -- Dirk Gunsthoevel IT Systemanalyse phone: +49 (0)251 28446-0 -- Hammer Str. 13 fax: +49 (0)251 28446-55 -- D-48153 Muenster http://www.GunCon.de/ -- "Toto, I don't think we're in Kansas anymore..."

Well, well I'm getting different results under IDS 10.00.TC3 under windows. with 2000 locks onstat -g seg gives:- Segment Summary: id key addr size ovhd class blkused blkfree 1381386241 1381386241 c000000 5308416 215512 R 1278 18 1381386242 1381386242 c510000 8388608 904 V 1651 397 1381386243 1381386243 cd10000 8388608 904 V 14 2034 resident segment where the locks are is 5308416 bytesK = 1296*4K blocks 1278*4K blks used = 5234688 bytes with 2000 locks with 202000 locks onstat -g seg gives:- Segment Summary: id key addr size ovhd class blkused blkfree 1381386241 1381386241 c000000 23920640 216080 R 5823 17 resident segment where the locks are is 23920640 = 5840 4k blocks 5823*4k blks used = 23851008 bytes with 202000 locks therefore 23851008 - 5234688 = 18616320 bytes for 200000 locks = 93 bytes per lock. Clearly this has gone up for version 10 and possible version 9.40 as well. Still 100,000 locks = 9300000 bytes = 8.86Mb