This group is dedicated to solutions and approaches for high traffic, high performing Drupal sites. As such, it will deal with a lot of information around the rest of a typical Drupal "stack" -- the operating system, web server, database, and PHP tweaks that combine to support the Drupal application.
This is not a support channel or a place to post bug reports.
If you think you have found a bug, use the issue queue for the appropriate project.
If you need support, see http://drupal.org/support for options.
In September 2010 we had a helpful discussion around ways for high-traffic sites, especially sites with external cache layers like Varnish or a CDN, to get usable node access statistics.
That discussion began with Pixel Ping and a Drupal integration module. I've put together the basics of another module now, one that allows you to sort by Facebook shares.Read more
The standard function for making a http requests in Drupal is drupal_http_request(). This works well for simple things. But if you want to send a request out & you don't care about the response back, this built in library isn't the best option; or if you want to do 10 requests at once the standard library isn't the best option either as you have to do each http request sequentially, one at a time.Read more
Nginx has 2 caches:
A proxy cache when you're proxying to another HTTP server.
A fastcgi cache when you're "proxying" to FastCGI.
This is a native cache not an external one. Hence you can get high performance caching without the additional complexity of having another moving part on your setup. Thus making potentially making things like Varnish superfluous.Read more
I've got a Mercury 1.2 site set up on Linode and just installed a new site. In some page loads I get extremely long delays. (30 seconds or more) On other page loads, they come up almost instantly. I know the Varnish 503 error is probably because it is waiting for Apache to respond. The question becomes, why is Apache so slow??
What is the best method or analysis package for tracking down these extreme slowdowns???
Just for information for all that are interested in high performance drupal and happen to be at DrupalCon London:
We're having two BoFs tomorrow, which are sharing one timeslot from 11:00 to 12:00.
The first part is:
DRUPAL PERFORMANCE AND SCALING by soyarma, which is a followup session to his talk "Damn quick drupal" (http://london2011.drupal.org/bofsession/drupal-performance-and-scaling)
The part second is:Read more
I need some assistance with my varnish (or at least so it seems like), for whatever reason whenever I use curl to check for varnish's "X-Varnish-Cache" I always get "MISS", I'm not sure when/what have changed in the past so it stop working but a while ago it was working fine no problem.
I post my varnish's default.vcl here: http://pastebin.com/6yJALh5B
any suggestions are welcome and not to just MISS/HIT but in general if you have any suggestions over my varnish config I'm gladly listen
mbp:~ alexus$ curl -I XXX.XXX
HTTP/1.1 200 OK
Server: Apache/2.2.15 (Red Hat)
I'm trying to benchmark a View on a MySQL server shared by a number of other developers, so I don't have the luxury of turning off query_cache_type since as far as I can tell, it's server wide and not restricted to per database.
I believe there's a way to turn it off per session, is there either a good way or otherwise, that I can set my particular development branch to operate with query_cache_type off.
Alternatively, a way to push SQL_NO_CACHE into Views either globally or per View would be fine.
Thanks for any advice :)
Very interesting. Memcache as a service.
If anyone happens to kick the tires on this with Drupal I'd be interested in feedback on how it works. I don't have time at the moment to take it for a test drive but it looks quite interesting.