On Tue, May 29, 2007 at 09:41:05PM +0200, Pavel Cahyna wrote:
>
> I also observe very poor scaling down of the status command. I have a
> workspace with 17507 files. There is a subdirectory with 17 files. In this
> subdirectory:
>
> $ time mtn status .
> (...)
> 71.72s real 68.37s user 0.81s system
>
> $ time mtn status
> (...)
> 91.40s real 85.19s user 1.78s system
>
> For comparison: the same 17 files, from a CVS repository. cvs has to
> contact a remote server across the Atlantic.
>
> $ time cvs status
> (...)
> 8.70s real 0.14s user 0.09s system
>
> This is lame. Why should status of 17 files take almost the same time as
> status of 17507 files?
Is inodeprints enabled for that workspace? ("mtn refresh_inodeprints".)
How large are the files/database?
Matt
_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
