A few more questions we have:
1) How does memcached deal with a change in IP of a server? Does that
invalidate the whole cache in the same way as if I added or removed a
server?
2) We are also concerned about the number of open apache connections on a
machine at a given time. Currently we hav
1) I'm guessing your comment "fear of potential bottleneck" was referring to
my comment ""not to have these servers bogged down in notifications". That
isn't really our main concern. Our main concern because of which we are
hesitant to go towards a full and proper implementation of memcache is
the other
servers to invalidate cache on a DB write.
Please let me know if we went wrong in our understanding somewhere.
Any tips or thoughts are greatly appreciated.
Thanks.
On Feb 3, 10:02 pm, Jason Sirota wrote:
> On Thu, Feb 3, 2011 at 9:10 AM, Dustin wrote:
>
> > On Feb 3, 2
Thank you for your responses.
In the last several days we have gotten a much better understanding of
memcache in general and how we use it.
A little more background to help you understand the current state:
We have 4 live servers that are all supposed to be identical. Our code is
in PHP. W
Our system has 4 live servers on a load balancer in an Amazon Cloud.
We are using memcached but don't understand it very well, previous
programmers implemented it.
Any user that goes to our site will be using one of the 4 live servers and
all are supposed to be in sync and have the same data. We
