Experimental music, photography, and adventures

Archive for November, 2006

You’re The Man Now, Dog!

Wednesday, November 29th, 2006

My photos of an Abandoned Diner in Northern Indiana have been featured in a “You’re The Man Now, Dog!” at ytmnd.com. I had never heard of a “You’re The Man Now, Dog!” and looked on the YTMND.com About Page, which quotes Wikipedia’s surprisingly interesting entry:

YTMND, an acronym for “You’re The Man Now, Dog!”, is a website community that centers around the creation of YTMNDs, which are pages featuring a juxtaposition of a single image, optionally animated or tiled, along with large zooming text and a looping sound file. YTMND is also the general term used to describe any such site.

(That’s not the interesting part, read the entry for information about the site’s past conflicts with the Church of Scientology, eBaum’s World, and others.)

The “You’re The Man Now, Dog!” with my photos on it can be found at http://abandoneddiner.ytmnd.com/. There is also a brief discussion of it.
At first, I wasn’t sure how I should feel about this. I was flattered that they used my photos, certainly, but initially, I was a little irked that nobody asked permission. However, they do reference my Abandoned Diner Photos Set on Flickr. I am going to take this as a compliment. It’s certainly not the coolest thing in the world, but I do think the music fits, or at least it fits the mood I was going for in the photos, which wasn’t sure I captured.

North Tower Loop Pool Rewot Htron

Tuesday, November 28th, 2006

Dave and I rode the North Tower Loop tonight, and then rode it again, backwards. It really is a completely different trail going in the opposite direction. I have ridden it that way a number of times, but not enough that I always know what’s coming up next.

On the way back, we were approaching a dip in the ground, which was armored with some rocks. The idea is, you’re supposed to ride on the rocks. Well, unfortunately, I was going pretty fast and couldn’t see too well, and I missed the rocks. My front wheel went into the dip and got stuck, and I endoed (I was thrown over the handlebars, end over end). I dismounted my bike in a pretty interesting way — I don’t remember unclipping, but I must have, because I wasn’t stuck to the bike, and I basically jumped over the handlebars to avoid running into them. I landed pretty well, hit my right knee slightly, which now has a small scratch on it.

I enjoyed riding the North Tower Loop backwards. There’s more climbing that way, but some sections are just a lot of fun. I had a few moments like I’ve described previously where it almost felt like I was floating above the ground.

We rode about 9.5 miles in 1:35, averaging about 5.8 mph. Pretty good for a night ride half on less-familiar trail.

Firefox Tuning

Tuesday, November 28th, 2006

My work computer only has 512 megs of memory, so Firefox’s memory usage has been a bit of a problem for me here. I found some tuning information today that I’m hoping will help.

What I’ve done (in about:config):

  • Set browser.sessionhistory.max_total_viewer to 0 (on my system it was max_total_viewers instead, I set both to 0). This seems to tell Firefox not to keep a bunch of back/forward pages cached for each tab.
  • Set browser.cache.memory.capacity to 4096. This sets the amount of RAM Firefox can use for cache. By default, it’s allocated dynamically, but I think that led to the memory usage growing over time.

At home, I’ve also done some performance tuning involving pipelining. This entry on the element14 blog talks about bout the max_total_viewer and pipelining tweaks. It also claims that the Firefox memory leak bug is a myth and that the max_total_viewer setting stops it. I haven’t taken enough time to examine the effects of these changes, but I doubt that. I definitely think there are memory leaks in Firefox.

I also found an incredibly detailed thread about tweaking Firefox. Some of the information there may be outdated, but it’s the most in depth discussion of the topic I’ve seen.

Finally, extensions are often the source of a lot of memory leaks in Firefox. Here’s a list of extensions that are known to be problematic.

Ear to the Breeze is proudly powered by WordPress
Entries (RSS) and Comments (RSS).