As of today, I’ve changed the address of my blog from just EricMartindale.com to a new location that will contain my blog posts in a new format. Don’t worry though, all your old links will still work just fine.

Why am I doing this? Well, there are a number of reasons why - not the least of which are some SEO (search engine optimization) adjustments that I’m in the process of making. However, the biggest and most important thing to you is the introduction of Eric Martindale’s Lifestream, which is the newest and latest feature of EricMartindale[dot]com. This new area of the site is called a Lifestream because it will show you everything that I’ve been doing lately, from shared posts on Google Reader to photos from Flickr.

I’ll be fighting at this weekend’s “Fight to the Finish II” (Greenville, NC), as the second event run by the Amateur Fight League. Tickets are still available, especially with some great deals available from AFL’s Online Store - don’t wait, make sure you get your tickets before the weekend. :]

I’m scheduled to weight in as a middleweight (171 - 185 lbs.), which is a step up from my normal weight (170). I’ve been lifting heavy and training hard, gaining some weight to meet Brian Ward in the ring in my third mixed martial arts fight. Since my last fight against Will Estes was deemed the most exciting fight of the night by StarNews, I’ve been training harder and working more towards my professional career as a mixed martial arts fighter.

Rest days start after my last training session on Thursday night, so I’ll be getting some well-needed rest and relaxation Friday to prepare for the weighin on Saturday morning at the Greenville Convention Center. Afterwards, my friends and I are meeting one of my RolePlayGateway staff members at the Olive Garden in Greenville to enjoy my pre-fight lunch. Then it’s off to rest (hoorah for naps), and then later that night - it’ll be fight time.

Get in touch with me if you’re out in Greenville and you’re interested in having lunch with us or if you want to show up for the fight (which is at the Greenville Convention Center, tickets will be available at the doors), you’re more than welcome to come.

Let’s do the damn thang.

Dear Search Engine Roundtable,

Since I subscribed to your feed (in early 2005), I have received and read every post you’ve made using my RSS reader of choice (Google Reader, currently). Your excerpts have been enticing, with well-written post titles and seemingly interesting topics. The idea was good, to aggregate content and discussions about Search Engines from multiple locations at one central blog.

Unfortunately, I’ve found that your articles are less informative than I’d have hoped, with frequent referrals to other locations where the conversations are actually taking place. Instead of effective bullet points and topic reviews, I find quick and hastily-written overviews of the content and discussion in question.

Not only that, but you’re only providing partial content in your feeds! When I come across your posts in my daily reading of over 500 posts, you’ve caught my attention with your title - and because you’re only giving me the partial article text, you’ve got me clicking through to your site (hoorah, ad impressions!). Unfortunately, half the time I’m wasting even more time by being forced to click through to yet another page to follow the conversation.

I rarely (if ever) find myself sharing your content, and from what I can tell from a cursory glance - you’ve never shown up in my shared items feed. (PS, when will I be able to control this page, Google? I hope this link juice means something in the future. Maybe even market that page in a bit more of a controlled fashion. I digress.) I’ve maybe starred one or two of your articles for future reading, but again - when I do finally read the posts, I find that I’m disappointed by your article quality and content.

What’s up with that?! Alright, rabid feedreaders and social media evangelists - tell me if I’m in the wrong here, but I’m going to unsubscribe from Search Engine Roundtable.

I just came across an artist’s work of a futuristic fantasy Tokyo that is overgrown with vegetation, and is amid reclamation by nature. Immediately, I thought that these images demanded a roleplaying game to go along with them, perhaps of the walk-through nature.

They came from a blog called Tokyo Genso (Tokyo Fantasy) - which has some altogether amazing works of art, so go check them out.

One of the sites I own and run (RolePlayGateway) has a pretty large forum, with several customizations and features that I’ve added on to the base install of phpBB3. As time went on, we continued upgrading the servers (moving from GoDaddy shared hosting to GoDaddy virtual dedicated servers, then onward to MediaTemple’s (gs), and now we’re on the second tier of MediaTemple’s (dv) hosting) in an effort to keep the hardware moving as fast as possible.

As I’m sure you know, hardware can be pretty expensive! One month, while on MediaTemple’s Grid Server, we racked up $600 in CPU time overage charges. (Ow.) Now that we’ve moved onward to bigger and better packages, we’re shelling out just about $100 per month for a rock-solid server solution that can be upgraded seamlessly in the future. But since upgrades can only go so far without being prohibitively expensive, I thought it was time to take a look at some of our coding approaches.

Enter memcache, the distributed database caching solution originally designed by LiveJournal to help them deal with massive databases and large volumes of users. DavidMJ has written some shiny ACM modules to help phpBB3 make use of some caching systems, and a memcache module was among them.

That didn’t work so well. It gave about a 50% boost to phpBB3’s performance (which was great!), but we were still choking the server, and ended up upgrading to a bigger and more robust package with MediaTemple. So I started looking into more options, and DavidMJ suggested xcache. So I go grab xcache and compile it, then enabled it in php. Bingo! There’s a 500% boost in our page compile times, and across most of our pages we’re now well under 0.1 second compile times. (With the exception of viewtopic.php, which frequently approaches 2 seconds due to bad coding on my part… this will be fixed soon.)

So now that I’ve got the thirst for speed, let’s take a look at how we’re performing. To do this, use the apache benchmarking tool:ab -n 100000 http://www.mydomain.com/my_page
This will test the URL you specify 100,000 times, and give you some feedback about how the page performs. You’ll end up with something looking like this:

Server Software: Apache/2.2.3
Server Hostname: www.mydomain.com
Server Port: 80
Document Path: /my_page
Document Length: 0 bytes
Concurrency Level: 1
Time taken for tests: 15.30100 seconds
Complete requests: 1
Failed requests: 0
Write errors: 0
Non-2xx responses: 1
Total transferred: 715 bytes
HTML transferred: 0 bytes
Requests per second: 0.07 [#/sec] (mean)
Time per request: 15030.100 [ms] (mean)
Time per request: 15030.100 [ms] (mean, across all concurrent requests)
Transfer rate: 0.00 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 15030 15030 0.0 15030 15030
Waiting: 30 30 0.0 30 30
Total: 15030 15030 0.0 15030 15030


Some tweaks to the default xcache config that I recommend:

Set the number of caches to one per processor on your server!
; set to cpu count (cat /proc/cpuinfo |grep -c processor)
xcache.count = 4

This post will be updated as I explore phpBB3 and more server side options. (I wrote part of this post, then stopped writing… and figure I’d publish it a couple days later anyway!)