Hi, Some off-topic comments from me... :)
Dnia 8-04-2009 o godz. 3:15 Jim Idle napisał(a): > Finally, the biggest single wins you can get performance wise are to > correct bad coding/algorithms in the application itself. This is where > the jrpof program s will help you (though you might be about the first > person on the planet to use them other than the authors ;). jBASE community is using that with success :) We do use it in 4.1.5.17, but not too frequently to be honest. We use also "SEAT.RESULT" monitoring from time to time, which is offered as part of T24 functionality. This is also nice thing and I wonder how it was done. The problem with jprof is following (notice jBASE 4.1.5.17, 32 bit version): jprof output files ~>500 MB passed to analysis are causing jprof to crash (Seg. violation). I think that it was not memory allocation and jEDI UD type driver problem, but I do not recall well. We have reported such problem, but CSHD issue was finally closed. Temenos offered us "SEAT.RESULT" way of monitoring and we are fine with it. I do not know wheter reported problem was fixed (I was not interested in checking that - we just produce smaller files if necessary). Both ways of monitoring external code (core jobs) are good to draw conclusions. Kind regards Pawel ---------------------------------------------------- Wyślij kurczaka na święta - Kliknij: http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fwielkanocnykurczak.html&sid=690 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
