|
From: Eyal L. <ey...@ey...> - 2003-03-14 08:19:33
|
My standard run takes about 15h, and in this period a single server deals with a few hundred clients. I need to know which valgrind error report belongs to which client, and the way to do it is to timestamp the reports. I added a line saying ==nnnn== Time: dddddd-hh:mm:ss to the start of the report and I find it very usefull. It was a worthy exercies as I found that I cannot simply access the c library (I am still to learn how to do this) but since I did have access to time() I displayed the rest using a simple function. Is there a standard was to request such timestamping? I would not mind learning how to properly add it to the package, with a proper --time-stap=yes option. Right now I find the most important bit (after correctness) to be the speedup of the main scheduler, most of the above 15 hours pass with the CPU at 98-100% idle. Is anyone working on this part currently? -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> |