You don't mention if you have port 8333 open.
"In" for that time frame sounds about right. "Out" depends on your peers as Kluge mentioned.
For comparison:
http://192.3.108.244/vnstat/index.php?if=venet0&graph=large&style=light&page=d
http://192.227.137.5/vnstat/index.php?if=venet0&graph=large&style=light&page=d
http://192.227.139.229/vnstat/index.php?if=venet0&graph=large&style=light&page=d
http://192.227.135.216/vnstat/index.php?if=venet0&graph=large&style=light&page=d
Topic: Bitcoin Core 0.9.2.1, 450 MB IN, 3 GB OUT, normal? (Read 1118 times)
It's likely uploading transaction queue and blockchain to multiple peers (8+) while you only receive one copy. Running a sync'd client is roughly like seeding a .torrent. You can force Core/QT specifically to reduce how much data it's sharing with an application-level throttling program like NetLimiter -- it functions fine throttled to ~3kb/s up, ~5kb/s down, keeping in mind you wouldn't be contributing anything significant to the network that way.
The network bandwidth tab in the console shows these numbers for a period of 18 hours: IN 350 MB, OUT 3 GB. Also, a month ago it synced 7 days of data for about 30 min, and recently it takes about 1-1.5 hours to do the same. I run it about once a week, because I don't want it to accumulate lots of unsynced data.
What is the client uploading so much? I thought the download should be more.
Any ideas?
What is the client uploading so much? I thought the download should be more.
Any ideas?
Jump to: