Open ConXO opened 10 years ago
Actually the Sync Time you set (10 mn / hours , etc) is checking the remote server, but indeed we try to keep changes on the local continuously. We'll check how to change that. And also maybe lower the cpu usage during this phase -c
So on windows 7 you don't have CPU peaks?
Yes i do, but I can't directly compare the two since my Windows 7 PC is more powerfull. I will try to make a better comparison.
Using similar hardware I do see the same problem in Windows 7. https://www.dropbox.com/s/nbvisqtu6tw4zwg/Pydio_W7.png .
@ConXO would it be possible to create a TeamView session so we could take a look on this behavior? contact me please.
Hi woj-spot, I set up a Teamviewer session. How do I contact you in private - are you on the Pydio forum?
Regards, Kristian ConXO
@wojt-spot How can I contact you private? You can contact me at: teknik (at) conxo.dk
I tried digging a little deeper into this using Ressource Monitor in Windows 7, and I observed that during the "Detecting local changes..." phase there is a lot of writes to C:\Users\user.pydio\pydiosync.sqlite-journal, which would indicate (a lot of) database updates.
Does the client recalculate hashes for all files and update the database for every "local changes" phase?
I have a problem with 0.8.4A on Windows XP, downloaded from: http://dl.ajaxplorer.info/nightly/sync/0.8.4-SNAPSHOT/Installers/0.8.4-A/ .
Setting up a sync job with 10 min. sync, Server Load low is fine and syncing is fine.
BUT: After completing the initial sync, Pydio is using 100% CPU every minute (55 seconds to be precise) for about 25-30 seconds, which makes the PC useless for normal work.
Hoovering over the Pydio icon when it's busy says: "... running: Detecting local changes...", but why does the client index local files every minute when sync is set for 10 minutes ? Even setting direction to Download Only does not solve the problem.
Logfile is filled with: 2766583 [PydioScheduler_Worker-1] INFO root - This pass took 34141 milliSeconds (Local : true) 2802623 [PydioScheduler_Worker-1] INFO root - PREVIOUS INDEXATION 2823881 [PydioScheduler_Worker-1] INFO root - This pass took 36438 milliSeconds (Local : true) 2857512 [PydioScheduler_Worker-1] INFO root - PREVIOUS INDEXATION ...
Workspace is FS with CIFS mount with Metastore, File Hasher and Lucene loaded. It contains 1.5GB in 4.100 files and 1.300 folders.
Just tried the same on a Windows7 32-bit, and the result is (almost) the same: It still makes a "Detecting local changes..." every minute, but now it completes in a few seconds.
This problem is not present in v. 0.8.3.