Hi Pawel, You have said
'In our case high 'lock collision' ratio on group locks is killing performance. JOB.LIST.x files suffer from multiple, concurrent 'SELECTs SAMPLE' (~ full scan) and multiple, concurrent READUs/WRITEs' I'm not sure what release you use at the moment but I would only expect to see the above problem towards the end of a job when a high number of agents are being used - at the start of the job a list is created and each agent takes 1/number of agents * total number of records as the agent work load - there should be no duplication of records across agents at this initial stage (but of course there could be a duplication of groups) When this workload is consumed a full select will take place on the JOB.LIST file and hence we can have more issues with collisions on groups, records processed by other agents etc. Are you sure that the problem is actually with the JOB.LIST table and not locks on BATCH.STATUS or BATCH - there have been problems in this area in much older releases and they should now be addressed. If the issue is with group locks on the JOB.LIST file and the overhead really is substantial then perhaps there is a logical argument to oversize the file to minimise the number of records in a group - to be worthwhile the increase in select time would have to outweigh the time lost to group locks. Cheers, John. -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to jBASE@googlegroups.com To unsubscribe, send email to jbase-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
