Zarathustra[H]
Extremely [H]
- Joined
- Oct 29, 2000
- Messages
- 38,877
Hey all,
For those of you who use Crashplan for your backup needs, I wanted to check what kind of speeds you are seeing, to see if my own install is performing as expected.
I have a 150/150 FiOS connection. I set my in app upload limit to 125Mbit (to make sure I had a little upstream bandwidth left for other things). My uploads started at ~85Mbps, but quickly dropped off, and now are averaging between 20 and 30 Mbps depending on when I check.
This is obviously a little disappointing. Is this just the way things are with Crashplan, or is it possibly Verizon is throttling me?
Could it be a local machine performance issue?
Backups are occurring from within a Ubuntu Server guest on my ESXi server. I ahve assigned it two cores of my 12 core (24 logical) low power Xeon system. (Base clock 2.26Ghz, turbo up to 2.8)
I told the client it can use 100% of the CPU, wheter idle or not.
Once core seems maxed out at 100%, the other core is hovering at about 20%.
I have disabled deduplication in the frontend.
Any thoughts, is this expected? Would throwing more cores at it have any effect?
Thanks,
Matt
For those of you who use Crashplan for your backup needs, I wanted to check what kind of speeds you are seeing, to see if my own install is performing as expected.
I have a 150/150 FiOS connection. I set my in app upload limit to 125Mbit (to make sure I had a little upstream bandwidth left for other things). My uploads started at ~85Mbps, but quickly dropped off, and now are averaging between 20 and 30 Mbps depending on when I check.
This is obviously a little disappointing. Is this just the way things are with Crashplan, or is it possibly Verizon is throttling me?
Could it be a local machine performance issue?
Backups are occurring from within a Ubuntu Server guest on my ESXi server. I ahve assigned it two cores of my 12 core (24 logical) low power Xeon system. (Base clock 2.26Ghz, turbo up to 2.8)
I told the client it can use 100% of the CPU, wheter idle or not.
Once core seems maxed out at 100%, the other core is hovering at about 20%.
I have disabled deduplication in the frontend.
Any thoughts, is this expected? Would throwing more cores at it have any effect?
Thanks,
Matt