I just want to go on record saying that none of Twitter's problems have ever been Rails problems.
postscript
Brandon Keene is right on.
July 10, 2008
I just want to go on record saying that none of Twitter's problems have ever been Rails problems.
Brandon Keene is right on.
July 10, 2008
Echoe 3 is out, right on the heels of Rubygems 1.2. It supports the new runtime vs. development dependencies, and works correctly with the Rubyforge 1.0.0 gem.
It still supports all the usual features like certificate chains, RDoc upload, changeset parsing, manifest building, and cross-packaging. Documentation is here.
By the way, Rubygems 1.2 seems pretty great.
June 22, 2008
It looks pretty small:
Lots of people claim they are bigger, like Hulu and Scribd. And others have published big traffic numbers: Yellowpages and Friends for Sale.
Let's break it down now, so to speak. First, we're not interested in rank, otherwise known as unique users; we're interested in pageviews. Can we get pageview data out of Compete? We can. First, take the visits per month:...
May 27, 2008
Francis Irving sent me a note about his work on a new Rails search plugin, acts_as_xapian. It uses the Xapian engine, which is a C++ indexer similar to Lucene. A particularly neat feature is built-in spellcheck.
I still plan to benchmark all these plugins on the Wikipedia dataset...it's been delayed by the new job. If anyone has a big piece of iron I could use for a couple weeks I would appreciate it (16GB ram, hundreds of GB of free diskspace, no production load).
May 26, 2008
This patch against RubyGems 1.1.1 improves memory usage by not keeping every unused gemspec permanently in memory. It should have low CPU impact as long as you do your gem requires up-front.
For MacPorts:
cd /opt/local/lib/ruby/site_ruby/1.8 curl http://blog.evanweaver.com/files/rubygems-memory-1_1_1.diff \ | sudo patch -p0
Incidentally, I used BleakHouse to track down which references were getting retained.
May 26, 2008