Drupal Implementations

[DJ]

CodeMasher's

A few years back at CodeMash I attended a session that used Drupal for
it's site. The site was geared around some sort of television or
video site. Unfortunately I can't recall what that site was.

Where this is leading to is trying to understand what that site or any
other sites using Drupal have experienced with 10K + users.

Does anyone have any experience with Drupal serving up content to 10K
+ users? If so, assuming the implementation is done right, does
Drupal perform well?

[DJ]

I did find the site that used a Drupal implementation: Zattoo

Can anyone speak to the load they deal with?

[Rob Reynolds]

I might be able to ask around at work...
____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

--
You received this message because you are subscribed to the Google Groups "CodeMash" group.
To post to this group, send email to code...@googlegroups.com.
To unsubscribe from this group, send email to codemash+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codemash?hl=en.

[nguyen nhu cuong]

thank you very must

2012/3/9, Rob Reynolds <ferven...@gmail.com>:

--
nhucuong

[Rob Reynolds]

I asked and received a response that we built one that supports a huge amount of users (x.com, which is a paypal/ebay dev community).

The downsides mentioned (and I can't intelligently speak to this, so hopefully the guy from work follows up):

"The downside to Drupal, when it comes to lots of authenticated users is it's really resource intensive. Essentially, once you have a lot of users logged in at the same time, the database gets hit really hard. The strategy for scaling at that point is adding more memory, cpu, disk speed etc."

[Jim Taylor]

Yea you really wanna try and offload to memcache and edge side includes as much as you can.

Jim Taylor
Rooty Hollow, Principal/Senior Engineer
p 614.432.8609
f 614.737.5327
http://www.linkedin.com/in/rootyhollow
http://rootyhollow.com


Drupal Camp Ohio registration is now open http://drupalcampohio.org/register

[Jim Taylor]

Yea you really wanna try and offload to memcache and edge side includes as much as you can.

On Friday, March 16, 2012, Rob Reynolds <ferven...@gmail.com> wrote:

[nguyen nhu cuong]

Do you have free ? because i don't have accout paypay

2012/3/17, Rob Reynolds <ferven...@gmail.com>:

> I asked and received a response that we built one that supports a huge
> amount of users (x.com, which is a paypal/ebay dev community).
>
> The downsides mentioned (and I can't intelligently speak to this, so
> hopefully the guy from work follows up):
>

> "The downside to Drupal, when it comes to lots of *authenticated *users is

[Dan Goldenbaum]

Hi,

Drupal does fine handling a large amount of users in the database. The issue you'll run into is how the system supports a lot of authenticated users at the same time. When Drupal is caching everything there is very little load on the server, but when everything that's being served up is hitting the database (when a user is logged in), things get slow.

There are various strategies for dealing with this. 

• As Rob mentioned, memcached is a good option (http://drupal.org/project/memcache)
• You can also use entity caching (http://drupal.org/project/entitycache)
• There has also recently been some work on offloading various database calls to MongoDB (http://drupal.org/project/mongodb) instead of MySQL
• And of course, you can always beef up the hardware

In short, Drupal is definitely a good platform for handling a large amount of authenticated users, but to get good performance, you have to do a little extra work.

[Jim Taylor]

We're also beginning to explore the use of ESI includes (which
requires Varnish). Results are promising, but on pages that are
heavily reliant on Views blocks you will still need to use other
strategies.

--