Scalability of a forum with node access

Events happening in the community are now at Drupal community events on www.drupal.org.
jcisio's picture

Hello,

I'm looking for a forum solution for a Drupal site. This forum must support moderating. Is there any lightweight solution, or is the forum access module scalable? Last year I had problem with a node access module. Is it correct that Forum Access sustains the same issue?

Do you know any big forum (a few dozens of thousands of nodes or more) that uses the Drupal forum?

Thanks.

Comments

There is an extra module to

omega8cc's picture

There is an extra module to add better performance and scalability to the standard forum module: http://drupal.org/project/forum2 but it is not compatible with node_access restrictions, however moderation should work, I think, just without advanced settings for forums visibility etc. Note: I didn't try that, just guessing from description.

Thanks, that's a good news! I

jcisio's picture

Thanks, that's a good news! I think remove the node_access restriction is the way to go for large forum, too!

forum_access is not a node access module

firebus's picture

it uses ACL instead, which makes it somewhat more scalable.

nanowrimo is a medium to large site that uses drupal forums. >100,000 nodes per year

i wrote a blog post in 2007 about the work we did to get it to handle traffic then. however, a lot of additional performance improvement has been put in place since then that i don't know the details of.

Technically ACL is built on

merlinofchaos's picture

Technically ACL is built on top of Drupal's node_access system (it kind of has to be).

i guess that makes sense

firebus's picture

for some reason i remember the joins with ACL being much less painful, but i can't remember the specifics.

joins with node_access, data created by acl.

greggles's picture

I think you mean the joins with node_access were less painful because acl module reduces the number of records in node_access to be just the required values and not any duplicate values.

I haven't actually compared it in practice, but I believe that's the only architectural difference that might give the benefit you mention.

I look like OG takes a

jcisio's picture

I look like OG takes a completely different way. It does not use node access, but override the access handle with Drupal menu system. OG also have og_subgroups module.

Currently G.D.O. has more than 100K nodes and it scales. However, when many modules follow this way, it could soon be a nightmare when each tries to replace the core access function with its own one, tries to support every other ones. It's doable, I have a module supporting OG and core node access, while also imitate the workgroup access feature. But it's complicated.

What do you think?

Folks should ignore this

moshe weitzman's picture

Folks should ignore this post. It contains incorrect information all over. OG comes with OG access module which is provides private content through the node access system.

GDO no longer runs og_access module and thus is not subject to node access api.

Hey, I'm looking at OG.module

jcisio's picture

Hey, I'm looking at OG.module lines 189-193 alter the core menu to provide a minimum access control without og_access module.

If GDO does not runs og_access any more, what does it run now for the scalability? We're looking for advice from core developers like you! Thanks.

Nothing

michelle's picture

I'm fairly sure there's no private groups anymore. I remember a big discussion a while back about getting rid of them. If everything is public, no need for access control. :)

Michelle

Yeah, but there are still

jcisio's picture

Yeah, but there are still admins (and a dozens of other roles in case of L.D.O) who can edit any node in their groups. That's at least what I'm waiting from "forum moderators", beside the ability to edit any comment in any node in their group.

High performance

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: