Re: LOCKS

At 04:52 PM 21-08-98 +0900, Sahrul Hidayat wrote: >If we configure LOCKS, let say 1.000.000, Online allocates about 40 MB of >resident shared memory for LOCKS. So, When locks active i.e 6 users (i.e >result of onstat -k), the allocated of shared memory still 40 MB, even the >limit of locks doesn't reach the maximum ..?? or the allocation will be >smaller than 40 MB. It's obvious that you've seen the manual (good on you!) The next thing for you is to try it in person and observe the results. It turns out that locking is rather complicated, and that behaviours vary depending on version and product. The short answer in your scenario is that LOCKS sizes a memory structure which then may be allocated for storage of locking information by individual processes. The structure is fixed in size in versions <=7.3 (and may be dynamic in coming releases.) Use onstat to observe how processes consume lock table resources--by query rather than by user. A great place to play with a database that won't affect your production system is at Informix training. The beauty of the program is that not only do you get a whole database to yourself to put through its paces, but also an expert instructor who can explain this kind of thing to whatever level of detail you desire. _____________________________________________________________ Clem Akins (aka clem@informix.com) Menlo Park x5937 Customer Course Development Informix Software, Inc Last seen: Jammin' to Richard Elliot's sax in Mtn. View, CA