Re: [tlug] memcached / alternatives

[Miles Colman <mcolman@example.com>]

I guess I should have said that remote isn't caching as much as I expected. Anyway, I'm going to have to look at how to put things into cache more before I look at distributed stuff.

On Mon, Jan 21, 2013 at 11:31 AM, Miles Colman <mcolman@example.com> wrote:

Thank you Edward and Christian.
I have attached local and remote 'free' output, which shows that our local postprocessing machine is caching things, but remote isn't. Also, remote has been up 149 days with a load average of 1.07, mostly doing the same postprocessing tasks as me, so I think there is no shortage of stuff to put in memory.

I haven't yet done anything with varnished, redis, or memcached. Does anyone have an opinion about which one will offer the best performance with the least set up? I can follow detailed tutorials, but I'm not so good about leaping over gaps in tutorials or reading through manpages.

Thanks,

Miles

On Fri, Jan 18, 2013 at 1:49 AM, Edward Middleton <edward.middleton@example.com> wrote:

On 01/17/2013 10:30 PM, Darren Cook wrote:
>> If you are going to look at memcached I would look at varnishd[1], or
>> redis[2].
>
> Any particular reason you prefer these?

I have found varnishd to perform better then nginx, which is saying
something.  It is also designed to perform well in real world situations
were the dataset is larger then available memory.  Redis offers some
server side features you might be able to be leveraged to improve
performance.

Edward

--
To unsubscribe from this mailing list,
please see the instructions at http://lists.tlug.jp/list.html

The TLUG mailing list is hosted by ASAHI Net, provider of mobile and
fixed broadband Internet services to individuals and corporations.
Visit ASAHI Net's English-language Web page: http://asahi-net.jp/en/