RE: UDR Cache

Hi , > > Number of lists : 1021 > > PC_POOLSIZE : 2048 ... > > Total number of udr entries: 352. > Number of entries in use : 137 > >This problem is not related whit bad configuration "PC_HASHSIZE" and >"PC_POOLSIZE" ? >I heard that is to small PC_POOLSIZE but i'm not sure. Unless you have an enormous number of Application based UDR's PC_POOLSIZE is not too small, it's way too large. Here is a rule of thumb, pre-Cheetah for configuring the UDR Cache. 1. Count up the number of user created UDR's. (ie. Don't count the system created UDR's) 2. Divide that number by a value between 4 and 10, normally I use 4. 3. Find the closest prime number greater than the value you got in step 2, this is you PC_HASHSIZE. 4. Multiply PC_HASHSIZE by a value between 4 and 10, again I use 4. This is your PC_POOLSIZE. Based on this: > Total number of udr entries: 352. > Number of entries in use : 137 > You are not coming close to automatically cleaning your UDR cache. What this means then is that the only time you clean the cache is when Update Statistics is run, or you bounce the instance. So, every time the idjorgget function gets re-optimized, you get a new entry in the cache. Based on the output though, it looks like you have plenty of sessions using each version though, so cleaning the cache would not change anything. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list