[Csync2] speed of "-cr /"

[Aristedes Maniatis]

On 10/06/10 7:53 PM, Lars Ellenberg wrote:
> On Thu, Jun 10, 2010 at 06:29:08PM +1000, Aristedes Maniatis wrote:
>> >  On 10/06/10 6:02 PM, Lars Ellenberg wrote:
>>> >  >For -R, its just config parsing, and SQL.
>>> >  >
>>> >  >For -c, it is one lstat for every record fetched.
>>> >  >100000 lstat calls may take some time;-)
>> >
>> >  In that case we've come a bit full circle with this conversation. Where we started:
>> >
>> >  * why does csync2 ignore the 'include' parameters when running -c?
> why do you have 100000 "stale" no longer relevant records in your database?

They aren't stale, they are in a different group. Isn't that the point of having groups? So you can run one part of the configuration without having to run the whole thing? I'd rather not create a dozen config files with a dozen databases.

Could you confirm the csync behaviour for -c:

SELECT files which match path passed as argument
foreach file {
   lstat file
   if not changed then break
   if not match include/exclude parameters then break
   set dirty status
}

Have I got that right?


Ari


-- 
-------------------------->
Aristedes Maniatis
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A