Urbanbike

Recherche | mode avancée

À savoir pour Synchronize! Pro X 4.0.2

Une option à activer sous Tiger pour retrouver les performances d'origine…

dans
par Jean-Christophe Courte

image

J'avais trouvé une énorme (monstreuse même !) différence de vitesse sous Panther et Tiger tout en utilisant les mêmes scripts avec Synchronize! Pro X. Hugh Sontag m'a répondu aujourd'hui et tout se passe dans le menu Options/Extented attributes…
En gros, il suffit de cocher la seconde option, Copy extended attributes only when file data is copied plutôt que celle d'origine, Copy extended attributes when différent. Du coup mes sychros de dossiers entre ma machine et le serveur accessible via IP sont redevenues normales…
La réponse en entier…

Answer: Tiger and extended attributes.
The slower folder scan you see in Tiger is due to support of extended attributes. The behavior of Synchronize! Pro X regarding extended attributes is set by using the Options menu to choose "Extended attributes...".
If "Copy extended attributes when different" is checked, all extended attributes must be checked during the folder scan, which slows it down.
If "Copy extended attributes only when file data is copied", extended attributes will be copied when a file is copied, and the folder scan will be faster. However, if *only* the extended attributes and not the data are changed for a file, the changes to the extended attributes will not be copied, and your backup will not be completely correct.
Extended attributes will be likely be used by many applications for tagging files with useful snippets of information. For example, comments could be attached to a file using extended attributes, or the URL for a downloaded file could be included. Exactly what these attributes will be used for will be constantly changing, as applications use them for new things.
If you want it to be as fast as it was on Panther, set "Extended attributes" in the Options menu to "Copy extended attributes only when file data is copied".

Merci Hugh !

le 06/06/2005 à 08:30 | .(JavaScript must be enabled to view this email address) à Jean-Christophe Courte |