I'm investigating using DA on a site along the lines of http://www.komonews.com/communities . In my case, though, I'm covering about 750 communities. Someone on IRC questioned if there would be performance issues with that many subdomains and I have no idea. 95% of these will have only 1 node assigned to them (the actual community node). They exist more as potential communities than actual ones since I don't have enough content to cover them all.

So I'm wondering if these "placeholder" communities will hurt performance? Would I be better off only creating domains for communities that start getting content? It's kind of a chicken and egg thing... If the community doesn't have the space, there's no place to add content. So I'd prefer to have all 750 set up and waiting. But I don't want to kill my site, either.

Thanks,

Michelle

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Other than the node access overhead, I don't think so. We mainly ran into UI issues when you have 100+ domains, but most of those have been corrected.

I normally tell people to plan on 10% extra hardware power to account for node access. But beyond that, the number of domains shouldn't matter.

DA itself will add maybe 6-8 queries per page, but since it is fully compatible with anonymous page cache, this usually isn't a problem.

nonsie may have some better ideas.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

I think the UI should be ok. 99% of the time a node will be either on one subsite and the main site or just on the main site. So as long as people enter the nodes from the subdomain and I can somehow automate adding the main domain automatically, they shouldn't ever have to worry about the list of domains to make it visible in.

I've spent more time working with DA since filing this issue and I must say I'm impressed. I've run into a few glitches with Views and I have a feeling Nodecomment is going to be a big problem but, over all, it works quite well.

If nonsie wants to chime in, that's great. Otherwise this is fixed as far as I'm concerned. I mainly was hoping it wasn't "OMG you're going to completely kill the server if you have more than 5 subdomains!" kind of thing. :)

Michelle

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented

After we fixed the UI issues there's not much that would stop you from doing it. Certain things take longer (rebuilding node perms for example). Most of the issues have to do it workflow and figuring out what works for you. I've found Views Bulk Operations quite handy to replace certain default forms when I need to look up domain specific content/comments/users.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented
Status: Active » Fixed
michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Thanks! Sounds like this is going to work really well.

Michelle

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Yes, AFAIK, the overhead difference between 5 domains and 500 is non-existent. The quantity of domains doesn't make the load processes work any harder.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Thanks again. BTW, I hunted down the Drupalcon Paris video and that really made things click after flailing around in confusion for a while. You might want to link to that on the project page.

Michelle

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Link?

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

http://www.archive.org/details/SharingcontentacrossmultiplesiteswithDoma...

Michelle

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.