> In general I would advice you to be very carefull running multiple instances > of memory and > connection (yes, a connection to localhost is still a connection) consuming > entities on > one machine. In various scenarios this will produce unpredictable behavior.
> Why bother? 2% more memory is within the error margin, it could be virtually > anything that causes your MySQL process to use a little bit more memory in > the other case, maybe your test case is a little bit different, maybe the > new access patterns cause a different usage on the internal buffers, maybe > it's just random chance. > > The important thing is that you consume 1/10th of the CPU with caching, > which means the whole thing works as it should and takes load off your MySQL > server. Thanks for your advice and opinion, ''l figure it out more :) To unsubscribe from this group, send email to memcached+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
