Re: Access from two computers
| Newsgroups | gmane.comp.windows.eccopro |
|---|---|
| Message-ID | <[email protected]> |
>>Ecco has a complex way of synchronizing files ... >>if I remember correctly it slowed down the system because it constantly updated files. I think it depends. Network bandwidth is not likely a problem. But what he may be referring to is the huge disk and to a lesser extent cpu resources it takes to sync certain files, and how they can take a very long time to sync. In some files the .ecg can get huge and so can the .eco files rendering Ecco syncing effectively useless because it takes so long for the files to sync when opened. I haven't used syncing in years because my most important file doesn't play well with Ecco sync. In this particular case, the file uses a lot of rules and scripts that update many items every time the file is opened. So the .ecg has to handle a relatively large number of automatic changes every single time either file is opened. I suspect that this is why this happens with these particular files. As a rough example of what happens ... an unsynced file starts out at say <2mb. When the sync copy is created and opened, the .ecg grows to ~20mb (and takes about 10 minutes of heavy disk/cpu use to write). When that is closed and the original copy is reopened then closed the .ecg goes to say 40mb... then 80mb on the next round and so on exponentially. It never gets smaller, only larger. And both the original and sync'd copies soon get to be ~20-40mb themselves. It takes forever for Ecco to write the sync info on a file of that size maybe 10 minutes or more every time either copy is opened and it gets longer each time. Syncing is essentially useless. A "simple" file can sync very fast and use little resources. A "complex" file can render syncing effectively useless. So I think the amount of resources and time consumed with Ecco syncing depends on the content of the files. In some cases it is prohibitively consuming rendering syncing effectively useless.