For an application I have been working on we have noticed some limitations associated with using PhpRedis. When it comes to stack tracing and performance testing I have found it impossible to debug what happens after Drupal hands a request off to PhpRedis. Since Predis is a PHP library, it should be easier to trace what it is doing and how long it is taking to perform a specific task.
I have made a first attempt at a Predis implementation here in the patch file. I have tried to limit my influence on the module structure so that Predis support is something that is just "dropped in" and does not affect any sites that are currently happily using PhpRedis.
Feedback welcome :)
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | predis-support-2900277-7.patch | 37.1 KB | maniosullivan |
| #5 | predis-support-2900277-5.patch | 37.1 KB | maniosullivan |
| #3 | predis-support-2900277-3.patch | 28.5 KB | maniosullivan |
| #2 | predis-support-2900277-2.patch | 31.03 KB | maniosullivan |
Comments
Comment #2
maniosullivan commentedComment #3
maniosullivan commentedI noticed that I had not implemented pipelining correctly for Predis. Updated patch attached.
Comment #4
maniosullivan commentedComment #5
maniosullivan commentedI have added some basic support for a master slave Redis replication using Predis.
Comment #6
maniosullivan commentedComment #7
maniosullivan commentedUpdated some terminology in the README.
Comment #10
berdirThis has been finished on https://github.com/md-systems/redis/pull/25, merged and committed.