performance

Hi,

Playing with Aegir - it is a great tool, but want to make it on steroids: use boost Boost and Cacherouter+APC as an user object cache for all sites. I will not touch Varnish for now.
What is the proper way to make config that works? Problem is, that I am changing "platforms" on Aegir rapidly and moving "sites" between them often, but haven't found the way to configure them globally.

Thank you for your thoughts.

Hi,

i am doing conceptional works/thinking about building up a photo page. The idea is to grant all users access on all images up to 3000px (traffic limit ony daily basis, because i dont want users to exploit and batchdownload all images). Resolutions bigger than 3000px are only for premium mebers.

Hi Folks,

It was great seeing everyone last night. I hope you all had a good time.

I wanted to pick your brains about a topic I know we all love - scaling Drupal!

We are running our intranet on a webhosting provider. At first, the provider did not have our requirements at all (some Drupal requirements not possible on a shared hosting because it might affect other customers on that hosting). So paid him more to move from a shared hosting to an own server.

Hola gente!

Pues bien, habrán leído la noticia que Google va a utilizar para indexar sus sitios la velocidad de carga como un elemento más a medir. Si bien no es un elemento que va a pesar mucho en la determinación del PR (aparentemente menos del 1% del total de sitios se ha visto afectado hasta ahora), creo que es un tema de discusión interesante.

Ok, I've been using the Rules module enough to know that I really* like it, but I still consider myself at the playing-around level.
Why? Because I can't yet use Rules on a production site. It's cool, inspiring and really useful, but I don't know if my site will choke when Rules gets hit by 1000 visitors in one minute or what happens when I get a crazy amount of nodes.

So, I'm curious: Has anyone made performance checks on some rules?

This question is probably a bit on the beginner end for this group but you've all probably been in my shoes previously so hopefully you'll be able to help me out.

I have a site with 6,000 nodes and 15,000 users. I make liberal use of Views, CCK and Taxonomy on all my pages and I use normal drupal caching and views caching. I run this site on a single VPS however my CPU usage lately has been a bit high (10% on a regular basis) and I need to figure out what my next step is to scale so as not to get on the bad side of my host.

Attached file provides significant performance improvement and is a recommended patch for OP 1.7.1 installations.

Just overwrite the original noderelationshops.inc file under sites/all/modules/noderelationships with the one attached here. You will have to rename attached file, removing the extra "_.txt" at the end. Sorry, drupal.org security rules, made us add that.

Make sure to clear Drupal cache (from devel or via http://yourdomain.com/admin/content/clearcache) after you update the file, otherwise you will start getting some erros.

We're working on implementing multiple methods for improving performance on a Drupal 5 platform and I noticed that various user hooks are called repeatedly on each page request. I realized that neither Drupal 5 nor Drupal 6 implement a static caching mechanism for storing complete user objects as they do for storing complete node objects.

I'm sure there is a good reason for this, but I'm having trouble fully understanding why. Can someone help explain to me why this is not done?

Thanks,

I'm presenting a talk on Drupal "Performance and Scalability" at the March Meetup for the Sydney Drupal Users Group. In preparation I have produced a series of articles on various aspects of Drupal and the LAMP stack. I have tried to cover the field as best I can. Some of the material is from my own experience but a lot of it is from discussions which have taken place in this group. The articles are at a fairly high level in parts but do attempt to fill in the detail by providing links to other articles which do a good job of discussing the area.