Posted by Ian Holsman
Our kitchen was sporting a wonderful set of waterfulls coming out of the downlights in the kitchen.. of course.. it was 2AM when it happened..
here's hoping the insurance assesor will be kind to us ;(
not happy jack
Posted by Ian Holsman
I'll be presenting at the Open Source Developers Conference over here in Australia. (providing the presentations get accepted).
Feedback is welcome of course
Posted by Ian Holsman
Born 1st October.
Weight 7" 10.
Everyone is doing fine, I'm just slack on updating the blog.
Posted by Ian Holsman
We've moved in, most of the unpacking is done, but we don't have a free moment, ton's of stuff to do/fix on the house.
I stopped by the local apple store (god help me, it's only 50m away) and got a airport express, and finally got it to work to extend the wireless range. the error message was about distributing ip addresses. what it meant was that you need to have your main airport base station doing NAT and DHCP (instead of just doing DHCP).
Posted by Ian Holsman
till we move into our new house .. pics here. Of course there are dramas, Mish just noticed that the color of the carpet being laid today is not the one she wants.. so.. we might be living in a hotel for a day or two I guess ;( This site will probably be down for a day or so until someone updates some routing tables, and we get the ADSL connection sorted out. FWIW.. it has been ~9 months since we signed on the dotted line ..
Posted by Ian Holsman
an article in Technology Research Network describes some research done by the Max Plank institute on how to avoid large failures (meltdowns) of your infrastructre by intentionally taking off some machines off the air before your the entire thing fails.
He describes how this couple apply to power grids, and the internet as a whole, but I think it could also apply to a companies site. Most large sites are not just a simple webserver serving requests. They have a myriad of machines all with specialized purposes and shared between different public serving applications.
We've seen on some of our stuff how a single query (no i'm not telling which ;-) can bring down other unrelated sites due to them using a shared component right down at the bottom of the food chain. I guess the trick is to find out which machines are actually 'generators' and which are 'transmitters' and trying to shutdown some generators before they take down the transmitters further down the line.
update: .. the actual paper is on Arxiv
Posted by Ian Holsman
yeah.. this is going to get old quickly.. this was from a post on the nanog mailing list.
The Cost of Internet Transit in…
| Commit | AU | SG | JP | HK | USA |
|---|---|---|---|---|---|
| 1 Mbps | $720 | $625 | $490 | $185 | $125 |
| 10 Mbps | $410 | $350 | $150 | $100 | $80 |
| 100 Mbps | $325 | $210 | $110 | $80 | $45 |
| 1000 Mbps | $305 | $115 | $50 | $50 | $30 |
and the EU is about the same as the US.
another reason why Australia has bandwidth caps I guess...
Posted by Ian Holsman
ok.. I wanted to buy a 2 books online from over here in Australia.. I went to check a local online book store Dymocks to order them.. on a off chance I also went to amazon and compared it (same ISBN's) ..now here is the interesting part.
the books (after currency conversion + postage) were 25% cheaper to get them shipped across the pacific than from sydney .. and that is with a US$21 shipping charge which is slightly less than the cost of the books themselves?
Oh.. and dymocks didn't even have one of the !@@##$% books in stock .. I can live with the 6-10 day delivery time...
Posted by Ian Holsman
cnet is testing some trackbacks feature so.. This Page has a embdedd RDF in it.. so lets see if I need to get funky with it
Posted by Ian Holsman
$50/month for a 15Mb/s link to your home. Thats ~10 times faster than a standard DSL link... at the moment it's just a town in texas somewhere, but in ~1-2 years it will be available for most people (read Silicon Valley)
What *IS* important is latency.. how do we get the page out FASTER with minimal delays...
when modems were the majority, it didn't really matter much how fast your server was, the major bottleneck was the size of the HTML (and images) being pushed down the users end. (be it a T1 or a 56k modem).. basically 10 seconds for 50k. now.. the pressure has moved back to the server, and speeding up your applications, as that is where the large percentage of the wait will be.
source: http://news.com.com/Verizon's+fiber+race+is+on/2100-1034_3-5275171.html