Comment 45 for bug 131094

I'm still seeing an unexceptable amount of I/O.

For instance. I thought timing a git clone with tracker on and then off would be a good test. So I did:

time git clone git://git.kernel.org/pub/scm/git/git.git

Only to realize that tracker didn't start indexing until after the clone was done. That's ok. So, I thought I'd do:

date; time git clone git://git.kernel.org/pub/scm/git/git.git; date

instead, just to see how long after the clone was done tracker would keep indexing. I didn't get that far though. I did a "rm -rf git" while git was indexing and punding the disk and thought I'd wait until it was done. It took several _minutes_ (I don't know... 5? 10?) during which the disk was working frantically all the time.

:(