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 this all-day workshop, top experts with years of front-line experience building large-scale Drupal deployments show you the best known practices for running fast sites for a large volume of users. Starting with a blank Linux virtual server, we will work through the setup, configuration and tuning of Drupal using Varnish, Pressflow, Apache, MySQL, Memcache and Apache Solr.Read more
We are setting up a server farm on EC2 to host a site built on Drupal 6. I am reaching out to the this community to seek help in setting up the MySQL master-slave replication where Drupal will write to the mast DB and read from the slave DB. Has anyone done this successfully on EC2?
We are using Scalr.net as the front end cloud application and its lets you set-up the MySQL master-slave instances quite easily. Where I need help is how to tell Druapl to write to the master DB and read from the slave.
Many thanks for help in advance.
The High Performance Drupal meetup has moved to Yahoo! at the Yahoo Center in Santa Monica and we're meeting this time on Tuesday, October 11, 2011. Join us!
The meetup begins at 7:30pm but the doors open a little earlier at 7pm for Users Helping Users, which is a chance for members of the community to help and be helped by others with whatever questions and problems they're having with Drupal. Several of us may be going to a local bar or restaurant after the meetup for a Drupal After Dark.
If you'd like to give a presentation, announce a job position or ask any questions of the group, please leave a comment below and plan to come a few minutes early. If presenting, be sure to bring your laptop (and power and display cables) and whatever else you need.
This event is free – in fact, there will be raffle prizes and food and drinks will be provided – and no RSVP is required. Those who sign up, however, will have last-minute details (if there are any) sent to them before the meeting. It's also good to know how many to expect so that we can arrange adequate seating, food, drinks, and so on, so please sign up by logging in and clicking the Signup button at http://groups.drupal.org/node/175834#signupRead more
(Referred from http://drupal.org/node/1255892)
I have been working on two development servers to try out a concept:
varnish -> apache > drupal, and
nginx -> apache > drupal, with
nginx -> (jpg, txt).
I have read all good things about running nginx with no modules to server Static Content (images, text files, etc) and it seems to work very well on server 2.
Both development servers are working very well. What I would now like to try is to combine the benefits of both but I do not know which is the preferred setup?Read more
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???