|
From: Bart V. A. <bar...@gm...> - 2009-04-23 19:50:06
|
On Thu, Apr 23, 2009 at 5:10 AM, Nicholas Nethercote <n.n...@gm...> wrote: > Some time in the last few days, on my ubuntu box, > helgrind/tests/tc19_shadowmem started running incredibly slowly under > DRD. It used to take a few seconds, now it takes about 5 minutes. It > happens with both 32-bit and 64-bit builds. It's still fast under > Helgrind. You are not doing justice to DRD with such comments. Anyone who looks at user comments or at the bug database can see that since the time DRD is no longer an experimental tool it is doing a great job. The performance of the DRD tool is acceptable: for some programs it runs slightly faster than Helgrind and for some other it runs slightly slower. The program tc19_shadowmem is an exception for which DRD runs significantly slower than Helgrind. Your e-mail creates the impression that at some time there would have been a change in DRD that caused it to process tc19_shadowmem a lot slower than before. This is not correct. About a month ago (March 10, 2009) you informed me via private e-mail that there was an error in the file drd/tests/tc19_shadowmem.vgtest which caused this test to be skipped by DRD. This error was fixed on the same day (r9337) and since then during the regression tests DRD runs the program tc19_shadowmem. After having read your e-mail I started looking at why DRD was processing tc19_shadowmem so slowly. By this time DRD should process this test program significantly faster -- on my PC it is now processed in 50s. Bart. |