February 22nd, 2004


LAX sucks; sweet land of liberty

LAX is the worst airport. Large, slow, dirty, smelly, lacking good food.

It's been awhile since I was here last, and I hope I won't be back here again for some time.

I wanted to sing the national anthem in the security line, and did a bit, but nobody else started singing with me, including Dina. I think I need to print out flyers with the words and distribute them next time in line. (Because honestly, I forget too. I mix up the lyrics to "America"... My country 'tis of Thee, Sweet Land of Liberty... Of thee I sing...)

Of course, if I passed out lyrics I'd have to censor certain words so I wasn't responsible for a mass singing of....

... the bombs bursting in air....

I don't think the TSA would be amused with that. Could they arrest me for showing patriotism, though, even appropriately censored?

Oh say does that star-spangled banner yet wave
O'er the land of the free and the home of the brave?

Free? Hah. Brave? Hah. We live in fear.

I'm not sure what would be more ironic:
  • Singing a song about freedom and bravery in the security checkpoint line.
  • Getting arrested for it.
  • Having to censor words in the song.
Anybody want to fly somewhere with me and try it out?

Oh, even more ironic:
  • That you're afraid to.
Fuck this police state. (and this airport)

Back home

Got back home about an hour ago. Man, the arrival flightpath into Portland was perfect... I saw Lake Oswego, OHSO, the west hills, 26 (with all the new construction), Forest Heights, highway 30, Vancouver, the bridge into Portland, etc... and it was nice and sunny.

Portland's so beautiful.

I'm looking for something... oprofile?

I can't for the life of me figure out this sporadic bottleneck I'm seeing on LJ's servers. When it happens I try to hunt it down and by the time I'm just looking around, it's gone. But it's seeming to happen more frequently lately.

DBs, memcaches, CPU, network... all seem fine.

So I have no clue why web processes are stacking up. Straced a few... see nothing odd.

What I'd like to do is measure the total wall time per file descriptor that the process spends blocked on. (which would require the tool knowing the different syscalls, and keeping track of what fds were which, or just looking it up as it goes....)

Can oprofile produce reports for that? I don't want to measure where CPU is used... I want to figure out where blocking is happening.