performance

Hi All,

I've been thinking about ways to build a really robust site spread across multiple cloud servers (common DB server) for redundancy and performance reasons.

I had an idea and I'm not sure if it's ridiculous or not:

1) create a multisite instance where all users, sessions and nodes are shared.

2) host each subsite on its own server

3) set up the subsites based on task, so that heavy processing can be done (many modules say) in one part of the site, and have less active modules/usage on another

I wanted to start a discussion on the impact of being logged in as "admin" and engaging in activities such as editing panels, creating views, and generally modifying a production site. It is easy to forget the memory demands this places on an operational server. Worse, I find myself often logged in from multiple Chrome windows while also logging in from Firefox and IE, all as admin.

Can someone help enlighten the group on the RAM impact of being logged in as admin in multiple Chrome browser windows, plus Firefox at the same time, all the while making significant site design changes?

I am working on a web application which will primarily be used by authenticated users. The web application imports records from CSV files using the Feeds module, MongoDB was chosen to store this data because it is much faster to do the writes rather than in MySQL. The application is importing thousands of records every day really fast. The records are referenced to the users and when they log in, they can consult their information. The application is also used as an API for the mobile app.

I have a 17gb AWS EC2 Instance as the server.

We've got several events on the schedule, leading up to the end of the year. Check them out on Meetup.com: http://www.meetup.com/dug-to/

Toronto Tech Wrap-Up Party 2013 (Charity Event Supported by DUGTO)
December 3rd
https://groups.drupal.org/node/377558

December Meetup: Case Studies
December 16th
http://www.meetup.com/dug-to/events/148966502/

Hi all.

I've been tasked with building a high performance, high capacity website for a client and so have been reading up on best practices. I'm getting familiar with the cache based approach for both authenticated and anon. users, APC, varnish etc - however I'm finding it difficult to find best practices regarding non-cachable requests.

-- EXAMPLE --

Suppose my website were to give away 500 free donuts to the first 500 people who correctly answer a multiple choice question. This figure would be stored in a field called "QTY" on the "freebie" content type.

Hi guys, first time posting here after using these forums for several years with great success. I have been building Drupal sites for a couple years now, and performance has always just been okay for me. The most recent site I am working on seems to be slower to load than most. I am looking for advice on how to make this site load faster. It is not a huge and overly complex site, doesn't seem like it should be this slow.

It is the latest Drupal install, and all up to date modules. There are about 50 modules, if it helps to provide a list of those I can.

I would like to share the experience to improve the Drupal performance in here :P

as we know, NODE is the base of Drupal, therefore, the node will be the bottleneck of the system as the number of node increases. In the most cases, we have multiple node types, and also some of the contributed modules are apt to store other information into node, such as content_profile, which saves the profiles into node, taxonomy_node, which saves the terms into node, and so on. Even the worse, we have many users in system, and one user has more than one profile nodes, so it will be worse.

A brief summary of the idea:

Data within entities that do not need to be processed individually within a view (or better: are not required to be addressed individually in any case) should be stored in a single database table, rather than being spread over N tables like they would if stored by the Field API "the usual way", in order to reduce the number of (sub)queries or subsequent queries and hereby reduce the load on the site's database.

It seems that with the growing Drupal user base, the problems with CMS (flexibility) and speed (non functional requirement) seems to be growing. We made a SAAS where one can install a small module (http://drupal.org/project/paas) and the buy a service where we scan your site. We do this on 100+ metrics and in an academic way (lots of "r" graphs, no gradients :-)

We measure your site from a selectable EC2 location and really test the site insite out and outside in. We dont just say "use parallel downloading", we measure how many host you need to get the most benefit, no yslow wisdom! :-)

Although I am sure this is a perennial topic in this group, I would like to start (yet another) discussion on optimization of my.cnf. I really don't understand mysql at all, and I have found even the slightest change to the my.cnf settings has a massive impact on my server performance.

I could really use some advice on settings from the group. Hopefully this threat can grow and be useful to others in the future.

My setup: