I've heard that a lumpy VOC is not recommended by the MV Doc. It causes overflows and more disk IO. Not to mention the dreaded disk seek - oh no! If all you measured was your proc in the VOC, all would be good (on wood you should knock). But with a large proc in the VOC and your other entries in overflow, well then - now you can see the aforementioned performance blow!
*-----------* Of course, all that is overstated on most systems now. Disk caching is quite efficient (and large). In only the most extenuating circumstances would moving large items outside of the VOC have any non-trivial impact on your running system. - Dan -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Monday, January 07, 2013 3:45 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] How to check which sproc is called by user Explain more this performance issue of which you speak. How is a proc in a file different from the proc in the VOC? -----Original Message----- From: Ed Clark <u...@edclark.net> To: U2 Users List <u2-users@listserver.u2ug.org> Sent: Mon, Jan 7, 2013 2:43 pm Subject: Re: [U2] How to check which sproc is called by user Toad the wet sPROCet !! A lot of procs get run from the VOC, but for performance reasons it's usually suggested that the proc in the VOC be only a linkage that calls a proc from a file. (would you eat it with a proc, would you eat it in a VOC, I do not like green eggs and ham, I do not like them Sam-I-Am!!). Procs can be run from normal files, so you could track them with a read trigger on the proc file I think? The other idea that comes to mind is adding a line to each proc which writes out it's name/date/time to a file. On Jan 7, 2013, at 4:54 PM, Ravindranath Wickramanayake <ra...@rammutual.com> wrote: > Hi U2 Guru's > > > > Can I tell when a sproc was last executed or who executed it. If so > how. Some way to get statistics and access logs. Reason we are asking > this is we are having a session hang issue we have tracked it down to > a session user but have no clue which sproc did the call to trouble shoot. > > > > Thanks in advance > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
