![bitcasa infinite drive bitcasa infinite drive](http://stri.ms/photo/view/52640e6420b161382288996354.jpg)
That’s why I’m an avid user of the free version of Dropbox. Once I purchase a hard drive, I shouldn’t have to buy it again next year. Paying for the same hard drive every year doesn’t make senseįirst, let me tell you why I find Bitcasa’s model so appealing.
![bitcasa infinite drive bitcasa infinite drive](https://i2.cdn.turner.com/money/dam/assets/130805143558-bitcasa-cloud-app-1024x576.png)
Explorer integration, performance benchmarking, and streaming video playback:.I think the company chose a small cache size by default to minimize the problem, but the bottom line is that file copies don’t happen nearly as quickly as they seem to. I have to admit that I’m skeptical that this was just an oversight. The current implementation makes it seem as though files have been uploaded at hypersonic velocities but then saturates network bandwidth for hours as it struggles to fulfill the request with decidedly non-magical equipment. This is only a problem when the size of the file to be uploaded fits entirely within Bitcasa’s defined cache, but it’s still a nasty loophole. Bitcasa doesn’t throw up a warning flag on the play.
![bitcasa infinite drive bitcasa infinite drive](https://i.gzn.jp/img/2013/08/27/bitcasa-infinite-drive/11.png)
Once the file has been copied, there’s nothing to prevent the end-user from deleting the original. It’s not a problem that’s unique to Bitcasa, by any means. What is troubling, however, is the way Windows’ file copy system is leveraged to make it seem as though a file has been uploaded, even when it hasn’t been. That reality puts a damper on these sorts of services. I suspect this is a problem with NB itself, but this app needs a watchdog to play nice with others. I tried using a third-party tool to limit upload bandwidth, but NetBalancer wasn’t able to control Bitcasa’s speeds. Using Bitcasa to upload a file effectively shut off my ‘net for any other task. The bad news is that routers respond remarkably poorly to upload saturation, and mine is no exception. The good news is that upload speeds are excellent - my system was able to sustain a 100KB/s connection to Bitcasa, fully saturating my own upload bandwidth. This application sucks bandwidth like a fat kid on cake and it doesn’t like to share. That brings us to another problem - Bitcasa is an extraordinarily bad bandwidth citizen. At 100KB/sec, it’ll take me nearly two days to upload these files. In reality, however, the file copy has barely begun.
Bitcasa infinite drive movie#
If I click on the movie from the I:\ location, it starts to play. There’s a file on my I:\, the file copy dialog has closed.
![bitcasa infinite drive bitcasa infinite drive](https://www.extremetech.com/wp-content/uploads/2013/02/BitcasaCache-260x300.png)
The real problem here is that as far as the end-user can tell, the file copy is actually complete.