High data transfer and cpu activity while idling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Syncany |
Confirmed
|
High
|
Philipp C. Heckel |
Bug Description
After having uploaded about 200mb from my syncany folder to a remote (amazon s3, encrypted) location and restarting syncany, it produces a lot of download traffic (about 250kb/s, nearly all the bandwidth of my DSL connection) and some cpu activity.
$ uname -a
Linux jo-notebook 2.6.38-ARCH #1 SMP PREEMPT Mon Jun 6 22:49:29 CEST 2011 x86_64 Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz GenuineIntel GNU/Linux
$ java -version
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.2) (ArchLinux-
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
$ python --version
Python 3.2
Syncany is repeating the following terminal output:
FO : 4. No local changes. Skipping step upload.
11-06-15 12:49:03 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : DONE WITH PERIODIC UPDATE CHECK ...
11-06-15 12:49:06 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : STARTING PERIODIC UPDATE CHECK ...
11-06-15 12:49:07 | jo-notebook | PythonScript | TrayServRead | INFO : time 1308156547.44 - last req 1308156543.01 > timeout 6
11-06-15 12:49:08 | jo-notebook | LinuxNativeClient | NativeNOPThread | INFO : Connected to native server on port 50,023
11-06-15 12:49:08 | jo-notebook | LinuxNativeClient | NativeNOPThread | INFO : Sent request {"request"
11-06-15 12:49:08 | jo-notebook | PythonScript | TrayServRead | INFO : Client connected.
11-06-15 12:49:08 | jo-notebook | PythonScript | TrayServRead | INFO : Received request: {"request"
11-06-15 12:49:08 | jo-notebook | LinuxNativeClient | NativeNOPThread | INFO : Received response: null
11-06-15 12:49:08 | jo-notebook | PythonScript | TrayServRead | INFO : Doing nothing. That's what I do best :-)
11-06-15 12:49:08 | jo-notebook | PythonScript | TrayServRead | INFO : Sending response: OK
11-06-15 12:49:12 | jo-notebook | PythonScript | TrayServRead | INFO : time 1308156552.45 - last req 1308156548.01 > timeout 6
11-06-15 12:49:12 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : repository has not changed locally. No need to upload.
11-06-15 12:49:12 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : 2. Downloading update lists ...
11-06-15 12:49:12 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : 3a. Analyzing updates & looking for conflicts ...
11-06-15 12:49:12 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : 3b. Updating client DB entries ...
11-06-15 12:49:12 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : 4. No local changes. Skipping step upload.
11-06-15 12:49:13 | jo-notebook | LinuxNativeClient | NativeNOPThread | INFO : Connected to native server on port 50,023
11-06-15 12:49:13 | jo-notebook | PythonScript | TrayServRead | INFO : Client connected.
11-06-15 12:49:13 | jo-notebook | LinuxNativeClient | NativeNOPThread | INFO : Sent request {"request"
11-06-15 12:49:13 | jo-notebook | PythonScript | TrayServRead | INFO : Received request: {"request"
11-06-15 12:49:13 | jo-notebook | LinuxNativeClient | NativeNOPThread | INFO : Received response: null
11-06-15 12:49:13 | jo-notebook | PythonScript | TrayServRead | INFO : Doing nothing. That's what I do best :-)
11-06-15 12:49:13 | jo-notebook | PythonScript | TrayServRead | INFO : Sending response: OK
11-06-15 12:49:13 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : DONE WITH PERIODIC UPDATE CHECK ...
11-06-15 12:49:16 | jo-notebook | RemoteWatcher | RemoteWatcher | INFO : STARTING PERIODIC UPDATE CHECK ...
description: | updated |
Changed in syncany: | |
importance: | Undecided → High |
milestone: | none → 0.1-alpha |
assignee: | nobody → Philipp C. Heckel (binwiederhier) |
status: | New → Confirmed |
The repeating output is quite a normal behavior:
- It is polling for changes at the storage.
- And sending NOPs to the python client so that it doesnt die (this is ugly, but necessary!)
It periodically retrieves a list of files from the storage (S3) - every 15 seconds - to check if there is something new. The high bandwidth is caused by the amount of files in the bucket... But 200kb/s is a lot.
I just took a quick look at the implementation of the S3StorageManager and it seems that there's a way to fix this. I'm on it :-D
Thanks for reporting.