You can simply copy the entire data directory from an existing bitcoin-core installation on another machine over to your machine, then start the bitcoind daemon.
Be aware you'll want to create a backup of the wallet.dat file from the destination machine so you don't inadvertently overwrite it. You may also want to confirm the bitcoin.conf settings work for the destination machine. Specifically, you may want to modify the rpcpassword, memory configuration, etc.
On Windows, the data folder is installed by default into %AppData%\Bitcoin
You may want to ask yourself whether the bottleneck is really your connection, or you CPU. While the blockchain is large, for most people, the bottleneck is the verification of the blocks/transactions rather than network speed. – Jestin – 2017-11-17T19:50:39.660
1My CPU usage is about 15-20% while running the application so I was thinking more about the download speeds. – Regmi – 2017-11-17T19:52:48.690
3@Regmi It's like I/O bound, rather than network bound. Block validation needs very large amounts of database operations, which often translates on the CPU waiting for disk. You can often improve this by increasing the
-dbcachesetting. – Pieter Wuille – 2017-11-18T00:29:18.480Increasing the cache size helped quite a lot, thanks! – Regmi – 2017-11-18T06:10:54.823
@PieterWuille The processing of the last blocks, Oct-Nov, took the longest and yes, those depended very much on my hd throughputs. I should have used an SSD but the node is up and running now, thanks. – Regmi – 2017-11-19T20:54:51.300