Hi all,

I fixed all memory leaks for the import of the batch system and for the first function of the batch system (create_pin). I fixed mainly the database module. The major problem was that I never freed the statement handles. I commited the stuff today to CVS HEAD. Here are some performance notes:

- import of 1000 users: 8 minutes (including swapping)
- create_pin for 1000 users
     2:30 minutes for workflow calculation (postgres uses >80%CPU)
     18 minutes for create_pin itself (postgres uses 40-60%CPU)

The mainproblem is usually my old notebook if I start with performance tests. During all tests the OpenCA daemon itself uses 34m (RES) and 27m (SHR) of memory (taken from top). So there is no memory leak. The only problem is the poor performance of my database or perhaps a bad database design. Nevertheless the new problem is the database design but I think there are more people who can fix database problems than memory leaks in Perl.

BTW never test with firefox and OpenCA (batch system) on the same machine. Firefox uses busy wait and creates in this situation more than 80% CPU load. Konqueror is much better in this situation and consumes nearly no ressources.

Chris, does it be possible that you only test create_pin from CVS head?

Best regards

Michael
--
_______________________________________________________________

Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704       Unter den Linden 6
[EMAIL PROTECTED]   D-10099 Berlin
_______________________________________________________________


------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to