I know I previously looked to see if I could get memcached to report what it
has cached, but I didn't find anything.
Eric
On May 14, 2012, at 12:53 AM, Christian Hammond chip...@chipx86.com wrote:
Hi,
Sorry, been on vacation this week.
I'm not sure if memcached provides an easy way to
Hi,
Sorry, been on vacation this week.
I'm not sure if memcached provides an easy way to see what's in the cache.
We don't have one. Sounds like memcached was the bottleneck, though, with
only 128MB of RAM allocated. I'd definitely recommend more.
Have you made changes since our last exchange,
Hey Alfred,
This is a database configuration issue. I don't know the key off-hand, but
you can increase the max packet size in MySQL.
That said, we do have a 1MB limit for diffs now (but that's not what you're
hitting), as Review Board can get bogged down if too many people are
processing large
On Mon, May 7, 2012 at 12:33 PM, Alfred von Campe alf...@von-campe.comwrote:
On May 7, 2012, at 15:20, Christian Hammond wrote:
That said, we do have a 1MB limit for diffs now (but that's not what
you're hitting), as Review Board can get bogged down if too many people are
processing large
On May 7, 2012, at 16:56, Christian Hammond wrote:
Memory and how much of it that memcached can use is crucial. We cache a
*lot*, since fetching files from the repository, patching them, and
generating diffs is all very expensive. So the more that memcached can hold
at once, the faster
