begin quoting Carl Lowenstein as of Mon, Mar 14, 2005 at 10:31:06PM -0800: [snip] > None of this explains why it takes 20 minutes to compute the MD5 sum > of the hard-drive file within the K3b "write and check CD" procedure. > Nor does it explain why it takes 20 minutes to read the CD image and > compute its MD5 sum in the same procedure. > > There must be some weird software interference to make the whole > process take something like 5x to 6x the sum of its parts. There > should be little overlap between the CPU-bound MD5sum and the > I/O-bound disk reading.
Doesn't KDE and friends do IPC over a socket? Perhaps there's some communication going.... > If this demonstrates the advantages of ObjectOriented Programming, I > don't see it. I don't think it's an OO issue in and of itself. What is K3b written in? -Stewart "OOP special sin: Pattern-Happiness." Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
