Just a thought - is there some virus-scanning software involved, that feels a need to scan every file opened?
Sent from my BlackBerry® wireless device -----Original Message----- From: Lluís Batlle i Rossell <virik...@gmail.com> Sender: fossil-users-boun...@lists.fossil-scm.org Date: Thu, 29 Sep 2011 09:55:45 To: <fossil-users@lists.fossil-scm.org> Reply-To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Scalability, a single file commit and lots of disk reads On Thu, Sep 29, 2011 at 01:45:29PM +0800, mjbmik...@gmail.com wrote: > It is the Windows version. > > I'm currently in the process of commiting a new 0 byte file to an existing > 2GB repo and Windows task manager says that the fossil process has read >3GB > of data since I issued the commit command several minutes ago, and it's still > running. > > First it read the the entire physical directory structure, then the entire > repo file. It then prompted for a commit comment, then started to read the > entire repo again. > 5GB so far. > Looks like it has started to read the entire repo again. 8GB and counting.... Maybe your filesystem or fossil/sqlite don't know about fseek? :) Do you see any fseek-kind-of syscall? As for the directory structure, it depends on whether you have the mtime-changes setting enabled or not, too. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
