Hi, I do not want to sound silly, but for me (user's perspective) there is no explanation of 1 minute time to show this kind of information (native locking discussed).
I agree with everything what Jim said, but still I can not understand why it takes 1 minute :) Can not Temenos improve this command? There is really no way? I think (from truss output) that most of the time is spent on finding out/showing last column (port number which is keeping lock on requested resource). Temenos advised us to use some other variation (LIST-RECORD-LOCKS or something) - one that does not display last column. This worked much faster. So locking information can probably be collected relatively quickly. I can send truss output from our busy server to anyone who is interested and want to check. You will notice that temporary files are opened thousands of times (there are circa 1200 ports during a day). I think that algorithm used to show last column is O(N^2) = check for each lock possibility of collision with other port. I am guessing a bit, but it would be highly imperformant if it is like that. Even if I am wrong with my guesses, I will claim that 1 minute time to show basic locking information seems to be far too much (server is damn fast). Kind regards Pawel Dnia 5-06-2009 o godz. 20:06 Jim Idle napisał(a): > [email protected] wrote: > > Hello > > i need the name of the table that keeps item locks. when i do a SHOW- > > ITEM-LOCKS it takes forever, but i am thinking if i can get the table > > then i'll do a select query to select a particular record, hopefully > > that'll be faster. > > > There is no spoon (points for knowing the reference). > > Why it takes so long is: > > 1) You should not need to run this command very often; > 2) It asks all the processes to to dump their lock information in the > proc directory (simplistically speaking) , then iterates it, so it is > waiting for processes to respond to the requests; > 3) Greg is a fat bloke with no mates, though he is going down the Gym now; > 4) See 1) > 5) Er.... > 6) That's it.. > > Seriously though, your question implies that you are trying to use this > command a lot and you really should not be. SHOW-ITEM-LOCKS is debugging > tool really and though for 20 years I have been telling people not to > write background processes to 'monitor' things, it seems to be every > programmers dream to do so. First, ask yourself why the response time of > this command matters to you; if you have processes locking up, then you > almost certainly have an application problem that you need to debug. The > problem with this sort of diagnostic is that it engenders the idea that > the fix for a problem that needs it is the kill command :-( > > SHOW-ITEM-LOCKS asks all the processes on the system for information > that cannot be gleaned directly from the lock table, hence it waits to > gather the information. Perhaps LIST-ITEM-LOCKS will be quicker for you, > but definitely ask yourself why the response time of this command is > important! > > Jim > > Kind regards Pawel ---------------------------------------------------- Lato 2009 nadchodzi. Wybierz swoje wymarzone wakacje. Sprawdź oferty: http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fwakacje2009.html&sid=752 --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
