I am new to the world of Memcached clusters
If I have a php web application that is using memcache - how does it does its hash and decide what node to check for a particular value to avoid having to check them all.
Bonus: How can I easily add a node in a way that avoids having to rebuild all the hashes.
Similar to how a memcache server can stampede a db after a missed hit.
Should I ever expect high traffic from my CDN(s)?
I am changing CDNs and I would like to preload some content to AWS Cloud Front so that my origin server is not hammered during that transition. Any tips?
I don't know much about DNS administration, etc, however I know about best practices in application programming.
Currently, in my company, we have 6 servers respectively named :
That's fine.
However, the sysadmin asked us to handle those random endpoint in our application, it means, that we need to pick randomly a server from within this list.
It looks bad to me, because whenever we need to add a server, we need to edit our application (even if it's just a config file), but I think application should not be aware of such things, similarly to entity should not know about persisting server.
My though is to use a dns load balancing, one domain, pointing to different ip
One endpoint: mobile.domain.com
The sysadmin told me that's bad or something like that, but I'm convinced it's the best solution, more it'll allow later geolocalisation load balancing which is great. By the way, randomly pick a server from a list won't prevent the server to shutdown since random is, just not random, and doesn't look efficient for me.
Thank you for your feedback, if you have arguments pro & cons I can use : )
I'm building an analytics package, and project requirements state that I need to support 1 billion hits per day. Yep, "billion". In other words, no less than 12,000 hits per second sustained, and preferably some room to burst. I know I'll need multiple servers for this, but I'm trying to get maximum performance out of each node before "throwing more hardware at it".
Right now, I have the hits-tracking portion completed, and well optimized. I pretty much just save the requests straight into Redis (for later processing with Hadoop). The application is Python/Django with a gunicorn for the gateway.
My 2GB Ubuntu 10.04 Rackspace server (not a production machine) can serve about 1200 static files per second (benchmarked using Apache AB against a single static asset). To compare, if I swap out the static file link with my tracking link, I still get about 600 requests per second -- I think this means my tracker is well optimized, because it's only a factor of 2 slower than serving the same static asset repeatedly.
However, when I benchmark with millions of hits, I notice a few things --
My questions --
a. Does it look like I'm maxing out this server yet? Is 1,200/s static files nginx performance comparable to what others have experienced?
b. Are there common nginx tunings for such high-volume applications? I have worker threads set to 64, and gunicorn worker threads set to 8, but tweaking these values doesn't seem to help or harm me much.
c. Are there any linux-level settings that could be limiting my incoming connections?
d. What could cause my performance to degrade to 250r/s on long-running tests? Again, the memory is not maxing out during these tests, and HDD use is nil.
Thanks in advance, all :)
EDIT Here is my nginx config -- http://pastie.org/1450749 -- it's mostly vanilla, with obvious fat trimmed out.