I think I've just found something. I had this set:

memory_replacement_policy heap GDSF

replacing this with:

memory_replacement_policy lru

got rid of the high CPU in 3.4 (works ok in 3,3).

I will try heap LRU.

Cheers

Alex

On 20/05/14 19:54, Alex Crow wrote:
Hi Amos, all,

I have set up a test box with latest 3.4.5 nightly. I get 95-100% cpu even with one client accessing the cache. I've attached a compressed strace of the child process in case anything is evident from that. Please tell me what else I might need to do to help resolve this issue.

I'm hoping this will help get to the bottom of why a number of people are having this issue on 3.4.x.

Any help much appreciated as always.

Alex

Reply via email to