Quote from: tl121 on December 19, 2015, 02:46:30 AM

Quote from: Holliday on December 18, 2015, 06:43:34 PM

Quote from: ArticMine on December 01, 2015, 08:35:54 AM

Quote from: Holliday on December 01, 2015, 08:25:20 AM

Quote from: ArticMine on December 01, 2015, 08:07:43 AM

hmm ...

My computer from 2008 has actually no problem at all keeping up with not just the Bitcoin blockchain but also the Namecoin and Monero blockchains all at the same time. Until August of this year I ran a Bitcoin node on a laptop from 2002 with a Pentium M processor, 1 GB of RAM and a 120 MB SSD. The laptop was so old that it was cheaper to replace the old PATA HDD when it failed with a PATA SSD. The laptop also has a floppy disk drive and a Windows 2000 logo.

Lack of education, indifference are part of the issue. The biggest problem is the replacement of desktop and laptop computers with mobile devices that while perfectly capable are crippled with DRM and propriety operating systems. A iPad in a good example of the latter, and can be far more expensive than a 3 year old laptop with a 1 TB SSD drive.

How much bandwidth is Core using per month? What are your maximum download/upload speeds from your ISP (and how much does it cost)? How many peers are you connected to on a regular basis? Do you have any special settings in your config file (fee rules or connection limits)?

I have dedicated hardware for my node (building computers is a hobby of mine, so I probably go overboard there), yet sharing Bitcoin data with my peers is where I am having issues. I've had to limit the number of peers that my node will allow or my internet service slows to a crawl for other purposes. I pay quite a bit for top tier (enthusiast) internet speeds from a major ISP.

Or, are you simply saying that your old computer can sync the chain at which point you shut it down?

I have 50 mbps down 10 mbps up with no cap residential ADSL. Running all three blockchains as a full node with ports open is about 400 GB per month.

Edit: I added the no cap option for an extra 15 CAD a month, The plan comes with 400 GB of data per month. Cost including a home POTS phone line is 132.50 CAD a month including all taxes.

I have similar speeds (faster download, same upload) and our discussion convinced me to increase the maxconnections allowed by my node to 50 (from 30). In a span of 6 days, my node downloaded 5 GB and uploaded 110 GB of block chain data.

The problem is that during this span, I often have a noticeable slow down of other internet traffic. During these times of heavy Core uploading, web traffic slows to a crawl and streaming video is out of the question. If my ISP offered a faster (upload) tier, I would purchase it, but I do not have the option. I live in a relatively (to the rest of the world) developed location. If I lived in a more remote (less developed) area, or had to send all of my Bitcoin traffic through ToR (I shouldn't need to explain why that could become a reality), I would have an even more difficult time running a full node. If the amount of data I need to share is drastically increased, I would have a difficult time at my current location.

I'm not great with the QoS settings on my router or perhaps I could improve my experience. Perhaps some of the changes coming to Core that I've read about will help. In the meantime, I've had to reduce the maxconnections allowed. I just can't see how anyone would want to drastically increase the amount of data needed to be shared while going through the same user experience as me.

I think Core should remain something that a Bitcoin enthusiast (willing to spend a decent amount of money doing so) like myself can continue to run semi-easily, even if circumstances arise which may make that more difficult (certain groups deciding that Bitcoin data should be censored, for example).

In other words, the network should remain robust ("lite and tight" as tvbcof would say).

Any quality peer to peer software, such as a reasonable bittorent client, comes with a control window that can be configured to limit upload bandwidth. If you set this to about 50% of your available upload bandwidth through your ISP then any problems with slow response will be avoided. For some years I used this technique with bittorrent clients and file sync programs. I was appalled when I started running bitcoin and discovered that the client lacked these elementary features. I was even more appalled after I complained and some of the core developers tried to make excuses for this sad situation. Lately, the talk from a (former?) core developer is that this deficiency will be "fixed in the next release" of Bitcoin Core.

There are two things you can do to get around this problem. First, do not open port 8333. This will eliminate the possibility of newbies leaching off of your limited bandwidth to download the entire block chain. Second, figure out how to set up the QoS features in your router. After you have done this you may then want to try reopening port 8333 in your router. With an open port and a QoS setting, you may still find a fair amount of upload traffic. You can limit this by configuring your node to use a modest number of ports. When I was running an open port on my node over a DSL connection, I found that about 30 ports total gave me about the same upload traffic as download traffic, i.e. my node was contributing as much bandwidth to the network as it was using.

If you are interested in running a full bitcoin node with an open port, be prepared for a bunch of hassles, up to and including being a target of a DDoS attack. If you are just interested in using bitcoin and don't want to get into a bunch of technical details it would be better to just run a lightweight client, such as Electrum or Multibit HD, both of which install and run quickly with no hassles.

Bitcoin XT has a bandwidth throttling option, which is a useful feature to have. Bitcoin Unlimited will be implementing this as well when it is released.