|
From: Nicholas N. <nj...@ca...> - 2003-03-14 08:37:32
|
On Fri, 14 Mar 2003, Eyal Lebedinsky wrote:
> 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
> 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.
Just choose an existing option and copy the way it's done. For example,
search for "--gdb-attach" and "VG_(clo_GDB_attach)" in the source ("clo"
is short for "command line 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?
Not really. Valgrind's threads implementation is not very fast, because
most programs don't really need it to be. And as simple as it is, it's
still one of the most complicated and problematic parts of Valgrind. So I
wouldn't hold your breath for improvements any time soon, sorry.
N
|