https://www.synology.com/en-us/knowledgebase/DSM/help/HyperB...
878 karma · joined May 20, 2012
@gregr
[ my public key: https://keybase.io/greinacker; my proof: https://keybase.io/greinacker/sigs/AEaI7oxgK8VaIDDjc4eSVszLrvyY0MlxXMtcAkH673Y ]
https://www.synology.com/en-us/knowledgebase/DSM/help/HyperB...
I'm glad it all worked out in the end!
(Note I'm speaking of reviewers in general, not the OP)
http://www.rassoc.com/gregr/weblog/2011/04/13/choosing-a-col...
1. Talk to your hosting providers and make sure they can support 32kW (or whatever max number you need) in a single rack, in terms of cooling. At many facilities you will have to leave empty space in the rack just to stay below their W per sq ft cooling capacity.
2. If you're running dual power supplies on your servers, with separate power lines coming into the rack, model what will happen if you lose one of the power lines, and all of the load switches to the other. You don't want to blow the circuit breaker on the other line, and lose the entire rack.
3. Thinking about steady state power is fine, but remember you may need to power the entire rack at full power in the worst case. Possibly from only one power feed. Make sure you have excess capacity for this.
The first time I made a significant deployment of physical servers into a colo facility, power and cooling was quite literally the last thing I thought about. I'm guessing this is true for you too, based on the number of words you wrote about power. After several years of experience, power/cooling was almost the only thing I thought about.
I would also add another rule:
6) Think of your job as a trader is not to make money - it is to manage risk. If you have an edge, the money will come. But if you fail to manage risk, you will fail.
http://blogs.adobe.com/lightroomjournal/2014/10/aperture-imp...
Anecdotally, my Comcast X1 is worlds ahead of the old Comcast boxes. Not perfect, but no longer so bad that I look longingly at Tivos. So, slowly but surely, they're making some progress...
Not a fair characterization, IMHO. She writes her own songs, and manages her own career. She might have mass market appeal, but I don't see how you can argue she's not a legitimate artist.
http://www.rassoc.com/gregr/weblog/2013/02/16/zero-to-postgr...
This will work over the internet between data centers if you're so inclined...depending on your traffic, a simple way to get started.
1. Some people ask for a discount, saying they're going to be long-term customers, they're going to blog about us all the time, and it's going to be great. 95% of these end up not being long term customers, and do not end up blogging about us all the time.
2. Some ask for a discount, and say (or imply) they'll go elsewhere if they don't get it. My thought is if a few bucks a month is the deciding factor, it's going to be hard to retain them in any case.
3. Some are polite about it, and just ask if there are any discounts available. They're going to subscribe anyway, but wanted to make sure they're not passing up a good deal.
I almost never offer one-off discounts any more, and very rarely offer any kind of public discount offer (and it's always for a limited time when I do). When someone asks I point them to our referral program, and to out partners who may offer a bundle discount on our product if you subscribe to _their_ product.
The benefit to this approach, in my mind, is that no one ever feels like they got ripped off because they had to pay full price - there aren't any public discounts available, so pretty much everyone pays full price.
But everyone fawns over their support ("I got a response in 3 minutes!"), and while that sometimes happens, it often does not. I've found recently the typical response time is around 15-20 minutes. I've had other tickets (including one that was critical) go for over an hour with no response, and finally I had to call them to see what was up.
Not saying they are bad - I'm a customer, after all. Just saying their support, in my experience, is not quite as amazing as some make it out to be.
It serves as a subtle reminder that the trial is about to end, while offering to help at the same time.
1. DO has no private network; all traffic between your nodes occurs via your public interface. In fairness, it looks like they're working on this (http://digitalocean.uservoice.com/forums/136585-digital-ocea...).
2. Linode's NodeBalancers are super handy if you need load balancing, and don't want to run your own. There are certainly some things I wish they could do (alerting comes to mind), but they're a heck of a lot better than running my own.