Redis on Justin Carmony

Talk: Blazing Data with Redis - Dutch PHP Conference 2014

Fri, 27 Jun 2014 20:00:12 +0000

Slides

https://speakerdeck.com/justincarmony/redis-dutch-php-conf-14

Resources

Demo GitHub Repo: https://github.com/justincarmony/fun-with-redis-2

Talk: Blazing Data with Redis - True North PHP 2013

Sat, 09 Nov 2013 20:00:32 +0000

Slides

https://speakerdeck.com/justincarmony/blazing-data-with-redis-truenorthphp

Talk: Blazing Data with Redis - PHP Tek 2012

Wed, 23 May 2012 20:00:23 +0000

This talk has a special place in my heart. It was the first talk I ever gave at a larger conference. The conference paid for my hotel and airfare, and I gave the presentation in front of over a hundred people. At the time, it was my personal goal to present at PHP Tek, and I had finally achieved it.

Slides

https://www.slideshare.net/JustinCarmony/blazing-data-with-redis-20

Talk: Blazing Data with Redis - Utah Open Source Conference 2012

Tue, 01 May 2012 12:00:00 +0000

I gave this talk at the Utah Open Source Conference in May 2012, the same year I presented it at PHP Tek.

Blazing Data With Redis (and LEGOS!) from Justin Carmony

PHP Workers with Redis & Solo

Tue, 10 Jan 2012 18:20:10 +0000

I’ve come across an awesome combination of tools for managing PHP Workers, and thought I’d share.

Why Workers?

Sometimes there are situations when you want to parallel process things. Other times you might have a list of tasks to accomplish, and you don’t want to make the user wait after pressing a button. This is where “Workers” can come in. They are independent scripts that run along side of your application, performing tasks, or “jobs.”

Published: High Performance Data with Redis and PHP - php[architect]

Fri, 01 Jul 2011 12:00:00 +0000

An article for the July 2011 issue of php[architect].

There are times when MySQL, or another RDBMS, cannot perform under certain circumstances, such as high volumes of reads and writes. While there are many other data store options, there is an excellent candidate when raw speed is a must. This article will describe when Redis might be a great fit for your application.

MySQL, Redis, and a Billion Rows - A Love Story

Mon, 23 May 2011 15:20:35 +0000

This last week we pushed live a very large architecture change for Dating DNA. For those who know me, and have heard me talk about the Dating DNA Scoring System, they know how big of a problem we faced. For those who don’t know, let me give some background:

The Problem

With Dating DNA, our goal was to display a compatibility score with every other user. This score is generated by taking two sets of answers to our 20 page survey, and running it through our algorithm. While it is super convenient for our users, this poses a problem. We wanted not only for people to be able to visit a profile and see a score, which is easy to generate a score on demand. We wanted our users to be able to browse other profiles sorted by their score with them. This requires us to pre-generate and store these scores, and then later query them.

Debuging with PHP, Stack Traces, and Redis

Mon, 10 Jan 2011 23:22:56 +0000

A cool new trick I found with debugging pieces of code and how often they get executed. We were running into a problem where an expensive query was being called more frequently than I thought it should. This query was only found inside of a single member of a class. However, this class, which retrieves a user’s photo album, is used all over the place. So it was really hard to determine exactly where the unneeded queries being executed from.

Creating Chatroom / Walls with Redis & PHP

Sat, 08 Jan 2011 00:15:16 +0000

Preface: This is not a step-by-step tutorial, but more of an outline on what I did. Also, I wrote this really quickly before heading off to dinner, so if there are parts that are unclear, or you have questions about, please leave a comment!

This last week has been a roller coaster for us at Dating DNA. We had an excellent holiday season, but with mass volume of new sign ups our servers started to slow down. Severely. Something you never want to have happen. So over this last week I’ve worked about 80 hours (though I’m a salary employee, woohoo… :P) and implemented a lot of new performance boots, and I have about four or five blog posts worth of discoveries I need to write. So before I forget them, I’m going to write them.