Dashboard data overload

Uploaded with plasq’s Skitch!

I don’t know what this is or how it works or why Sprint is involved, but man is it fun to just let the data just wash over you.

(Via kottke.org.)

President-elect Obama Calls for Swift Action on the Economy in Weekly Democratic Radio Address

Barack Obama delivered this week’s Democratic Radio Address Saturday morning, his first as President-elect.

In the address, President-elect Obama spoke about the need to put partisanship aside to solve the greatest economic challenge of our lifetime.

“Tens of millions of families are struggling to figure out how to pay the bills and stay in their homes,” Obama said. “Their stories are an urgent reminder that we are facing the greatest economic challenge of our lifetime, and we must act swiftly to resolve them.”

You can listen to the full address here.

Nice, now let’s see the podcast version

(Via Change.gov | Blog.)

Election maps

November 4, 2008

via patrickmosberg.com

(Via Follow Me Here….)

If you are in the US please Vote!

Conclusion? Unless you care a great deal about eking out every last byte (using a RAM disk, for example), LZJB seems like a much saner compression choice. Performance seem to improve, rather than degrade, and it doesn’t hog your CPU. I’m switching my ZFS volume to LZJB right now (on-the-fly changes - woo!) and will copy all my data so it gets the new compression settings. I’ll sacrifice some bytes, but that’s ok - performance is king.

Also, my theory that I’d always have idle CPU with modern multi-core chips so compression wouldn’t be a big deal seems to be false. Clearly, with gzip, it’s possible to hog your entire CPU if you’re doing big long writes. We don’t tend to do high-MB/s reads or writes, but it’s clearly something to think about. LZJB seems to be the right balance.

Some good notes on resource utilization in a large envronment