Photo Organizer

This is the bug tracker for Photo Organizer.
Tasklist

FS#298 - Add support for memcached

Attached to Project: Photo Organizer
Opened by Solomon Peachy (pizza) - Friday, 26 October 2007, 13:26 GMT-4
Last edited by Solomon Peachy (pizza) - Thursday, 26 June 2008, 16:18 GMT-4
Task Type Feature Request
Category Backend / Core
Status Closed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 2.33
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

http://danga.com/memcached/

It's basically a distributed key=value service. entirely In-RAM. (What happens when it fills? LRU?)

Initially, cache things that don't chagne often -- like usernames and folder names/parents but on a random photo page load, we have to hit several times.

This isn't a big deal now, but on high-traffic sites it can make quite a difference in performance.

Adding general support for this is a bit more complicated, as it would have to sit inbetween the querys and the database, so I'd rather just add it to a few hotspots as needed.
This task depends upon

Closed by  Solomon Peachy (pizza)
Thursday, 26 June 2008, 16:18 GMT-4
Reason for closing:  Implemented
Additional comments about closing:  There's always room for improvement, but the first parts are there. The search/folder browse improvements are a much more complex problem.
Comment by Solomon Peachy (pizza) - Friday, 26 October 2007, 13:31 GMT-4
There's an official PHP extension -- php-pecl-memcache.

We could also use it to store session info.
Comment by Solomon Peachy (pizza) - Friday, 26 October 2007, 13:46 GMT-4
-devel now allows one to specify a memcache session handler, or one can just use the default PHP stuff which of course can be memcache.
Comment by Solomon Peachy (pizza) - Sunday, 25 November 2007, 23:08 GMT-4
the default config file now includes a memcache example. I have it running on the peachy photography site, and it rocks.
Comment by Solomon Peachy (pizza) - Tuesday, 18 March 2008, 10:58 GMT-4
Initial candidates for caching:
*) userid -> info [un,fn,ln] (called once per page and almost never changes)
*) folderid -> info (and/or 'get_path_to_folder' cache)
*) albumid -> info (and/or 'get_path_to_album' cache)
*) photoid -> keywords
*) photoid -> tech_info

Then:

*) Search results -- the search query return everything, and it gets cached for a short time. we page back and forth from the cache.
Comment by Solomon Peachy (pizza) - Thursday, 26 June 2008, 15:50 GMT-4
userid ->info added
locationid -> info added
get_users_folder, get_users_album added
photoid->keywords added
get_path_to_folder, get_path_to_album added

Loading...