scaling

We're ll the process of moving our Drupal 7 online app platform site to a major cloud provider that will include horizontal scaling (multiple nodes for Frontend as well as multiple nodes for MariaDB). We're now considering the optimal solution to scale caching.

We are contemplating substituting standard memcache server with either internal Couchbase memcache server or Redis. The goal is to optimize performance of the site.

We are also contemplating upgrading from php v5.4 to php7.

Hi All!

I hope you had a wonderful holiday period :)

I've been thinking a lot about using multisite to reach the outcomes I desire in terms of performance/redundancy, and have firmed the concept up into the attached diagram.

Having never actually used multisite before I'm still coming to grips with some aspects, but as far as I can see there's no reason why I can't easily share nodes, users and sessions between the sites? Whilst allowing me to have certain modules turned on only for some subsites and not others?

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

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.

Setting up a Drupal Web site is pretty simple these days, until it gets popular, then you need to bring out the big guns and start finding and fixing the performance bottlenecks. In this article, we show some of the techniques that can allow your Drupal Web site to scale to the grandiose levels you originally hoped for.

http://bit.ly/d8jNw1

*Thanks to Christopher Cable for this story

Hello,

How does scaling work at Amazon if I start out with the smallest instance with a Mercury.

I have never used any of them, just doing my research on which way to go.

Would be as simple as clicking a few buttons on my Amazon control panel to get a bigger instance? :)

A note from the developer who oversees one of my Drupal sites. We could use your help.

Hello,

I have a rather burly Drupal based site that seems to be causing some
problems, today we had a major outage. There are many slow queries
and also mysql related iowait that causes server processes to hang, at
least that is the theory.

Here you can examine some of the stats on the server:
http://andric.us/load/localdomain/localhost.localdomain.html

You can see my iowait stats here, which are pretty high:
http://andric.us/load/localdomain/localhost.localdomain-cpu.html

we're mostly friendly. and mostly fun. but we're pretty geeky. in a cool way, of course. but this month we're a bit melancholy on the news Crystal is leaving us for Seattle. :-/

the good news is that we taped our meeting. ya, real geeky. but LA area is HUGE. and sometimes making it to the meeting in person can be difficult. so there you go... we're geeky but thinking about everyone that wanted to join us, but couldn't.

The March meeting is a combined meeting with the Vancouver PHP User Group:

Scaling Drupal : Notes from the field