|
From: Josef W. <Jos...@gm...> - 2006-08-22 19:54:50
|
On Tuesday 22 August 2006 18:18, Bart Van Assche wrote: > ... > This means that the memory consumption of the drd tool is proportional to: > - the number of threads running simultaneously. > - the number of segments allocated within a thread. > - the amount of unused memory allocated within the bitmap allocated for a > segment. When e.g. iterating over a byte-array, and only reading every > 1024th byte, only 0.1% of the memory allocated for the bitmap will be used > -- very inefficient. > > Or: it's not yet clear to me which of the above three reasons applies to > konqueror. Hmmm... AFAIK, konqueror does not do multithreading. Why does drd for the 1-threaded "segment" at process start already need to store read/write accesses? I would say that there can never be any race until a second thread is created. Or I am wrong and the drd tool is not storing read/write accesses for konqueror, but only the 500627 (*) mallocs with stack traces for potential later error messages. Josef (*) This is only konqueror startup, until the blank window appears (KDE 3.5.3). Just checked with callgrind... |