According to Joe R. Jah:
> What does htdig process do, when it does not change anything in the
> database or any other part of the file system that I can observe. For
> example, I observe changes to the time stamp and or size of the database
> only a fraction of the dig time. In about 90% of the dig time I do not
> observe any disk write. What is the bottle neck? What is it doing? Is
> it reading all that time? The entire dig is done on the same server that
> htdig runs. Working in memory shouldn't take long; does it?
Time to do some profiling on the code to see where it's spending all its
time!
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
