I keep my Zsh configuration in a Git repository. I have fast server hardware on a fast, reliable Internet connection in a data center that is less than 10 ms away- Seafile is significantly faster than Dropbox for me, and usually has no problem maxing out my 35 megabit-per-second FiOS connection. I’ll post some updated bandwidth numbers after I have a few more months to collect data. The data I have so far is pretty inconclusive, and I expect that everybody’s bandwidth use will vary quite a bit anyway. I’m not sure if Chris is just meaner to the Seafile server than I am or what, but we’ll be going way over the 6 GB I was expecting to see last month. The image above covers September 1 through September 8, and we’ve already used up over 18 GB of data transfer. I ended up taking a screenshot of September instead. This upload pushed the bandwidth consumption for August up over 30 GB, and totally ruined the graph on me. Then Chris’s new computer arrived, and she finally got around to moving all of her stuff up to the Seafile server. It was up at around 4 GB of traffic, and probably on its way to closing out the month with less than 6 GB of bandwidth consumed. It was going great for the first three weeks or so. I figured my bandwidth usage for August would be pretty typical, and I was hoping to get a screenshot of my Seafile virtual server’s bandwidth graph to show off here. I’m happy as long as my data is replicating correctly. Accounting for used space in the presence of compression and deduplication is a very hard problem.
Most of my Seafile libraries are replicated to my laptop, and everything seems to match up just fine. I wouldn’t be surprised if she has more than just a few gigabytes worth of duplicate songs and photos.
I’m going to hazard another guess here, and I’m going to say that compression and deduplication are saving her some space. Her local Seafile library is 31 GB, which is quite a bit smaller compared to what Seafile is reporting. My libraries are scattered all over the place, but Chris only has one, so hers are much easier to measure. I’m guessing the extra 8 GB is taken up by our file revision history most of our libraries are configured with 90 days of history. Even after manually running the garbage collector a few times, the server’s drive has over 40 GB of data. The web interface says we’re using a total of 32 GB between us. I’m not entirely sure how Seafile determines the amount of storage space everyone is using. I’ll probably think about doing the same thing some day, but my music collection is ancient, mostly ripped from CDs, and is terribly unorganized. She’s beating me by a pretty wide margin, but she has her music collection stored up there. I have about 9 GB worth of files stored in Seafile, and Chris has around 24 GB up there. I’ve had a few snags, but they’re all minor, and they’ve all been pretty easy to work around. Seafile has actually been working quite well for me so far. I think enough time has passed, and I figured I should report back on how things have been going so far. I started using Seafile over two months ago for all of my self-hosted cloud storage needs.
0 kommentar(er)
