84 karma · joined August 9, 2007
- You'll most likely run out of power well before you run out of physical rack space.
- You'll (hopefully) spend less time in the data centre than you think, especially if you have good lights out access, remote power bar access etc. If you're locating in a large city you can often get a better deal somewhere in the suburbs rather than downtown with very little downside (at least that seems to be the case here in London).
- Interconnects between racks can be awkward to get set up, and you can't necessarily get the rack next door when you want more space.
- Redundant everything will save you a lot of hassle, but gets quite expensive. In particular redundant power will save you from downtime when the data centre decide they need to take one of the power feeds down for maintenance (it happens), and setting up redundant (external) networking has the same effect. Having a second network for admin access prevents you from being locked out in some failure cases. Hot swappable drives are useful for systems which are awkward to take offline (e.g. database servers), but not massively useful elsewhere if you have good redundancy at the server level.
- Data centre rack floors are about the most unpleasant place to work you can imagine :-)
- If you can get a handle for how competent the data centre are at mitigating DoS attacks it's a useful datapoint. If they aren't on the ball an attack against anyone hosted in the same place will take you offline too. having said that, I'm not entirely sure there's a fool-proof way to determine this ahead of time.
- You can generally borrow a cart with a keyboard and monitor on it to wheel up to your rack, so no need to have those permanently installed.
- Keep a stash of network cables, cable ties etc. at the bottom of your rack - it's annoying to show up only to find you've forgotten that kind of thing.
- You may need to register authorised employees before showing up, so make sure you do that before taking your new intern to help rack a server. Expect them to ask for ID before letting you in.
- Data centres (at least some of them) will take deliveries on your behalf, so there's normally no need to get things shipped to your office then drive them out yourself.
My understanding is that using algae to do this via photosynthesis is limited by the fact that with wild strains you need to harvest and extract the biomass before you can get at the fuel, and you need to spread things out in a very thin film to get enough sunlight. Using modified strains helps solve the first problem, using (more efficient) synthetic photovoltaics, or another power source, with a process like this potentially helps solve the second.
To respond to another reply to this post, I don't think complex structures that maximise surface area would be necessary - you could just bubble air through the tank. As mentioned above, bubbling CO2 rich waste gasses from a power plant would likely be even more efficient.
One thing worth mentioning: anecdotally I've found that ActiveRecord can have an impact on performance far beyond the cost of the database queries, both by directly adding a reasonable amount of overhead and by instantiating a lot of objects internally which in turn triggers a lot of garbage collection. I wouldn't be surprised if that accounts for a fair chunk of what you're seeing.
Worth noting too that this is only one of a number of thin film solar technologies, and that silicon rather than thin film still accounts for the vast majority of all production.
http://www.guardian.co.uk/politics/2011/oct/03/george-osborn...
Maryland has a population of 5,773,552, c.f. 308,745,538 for the whole US, i.e. about 1.9% - my guess is they're actually talking about electricity consumption here, not overall energy consumption.
See http://www.songkick.com/info/jobs#systems_engineer for details. If you're interested, drop us a line at joinsongkick@songkick.com.
In our case this means working closely with developers, product owners etc. early in the development cycle to ensure that acceptance criteria are fully explored and agreed on, helping the engineering team build automated acceptance tests, which we use to drive development, and exploratory testing throughout the development process.
See http://www.songkick.com/info/jobs for details, and contact joinsongkick@songkick.com if you're interested.
A few minor tweaks to the visual design would make a big difference, but I'm sure you know that.
Longer term: maybe widgetise so people can put it on blogs etc.
In practical terms, you can just start hacking on the code yourself which will normally be available from a version control system somewhere, but when you've made changes you'll need to submit patches for consideration to the project maintainers at first. If you're unsure what format to use, just email to ask. For projects hosted on github you can just fork the project there which will make it technically easier to get patches back into the main branch. As you build up trust with others involved in the project you'll be able to get commit access to the project repository and make changes yourself.
As for IDEs etc, each project will have conventions and project metadata (makefiles, project indices etc.) suitable for a specific setup, so figure this out when you've picked a project and work with what's already in place as much as possible.
[edit] One other thing: it will be really hard to get started - getting up to speed with how a new piece of software works is difficult at the best of times and most projects aren't designed to make this easy. Persevere, as once you've got to grips with layout and conventions and got to know the other contributors things will become much easier.
This isn't necessarily a killer, but it means there's sometimes more work than you might like in scaling. There are patches to tune the garbage collector, and JRuby etc. may help, but ultimately you need to be much more aware of memory allocation than you might think.