<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Bookman Old Style";
        panose-1:2 5 6 4 5 5 5 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Arial","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.emailstyle17
        {mso-style-name:emailstyle17;
        font-family:"Arial","sans-serif";
        color:windowtext;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>So, if there were “many to many” data structures along with “one to many” structures (which node references are, if I understand them correctly), do I lose performance doing them with node references rather than hard coding the schema and interaction and storage?<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Basically, if I have the data structure and interaction already mapped out, and all the tables already designed, how much performance do I lose by setting up Content Types and Node References versus just creating the table manually, and writing PHP to control the data flow? <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Time-wise, I realize it’s much, much easier to do Content Types and Node References. It’s like 1/10<sup>th</sup> the time. But if Node References are going to hit the memory on the server too hard and cause performance issues and delays, then it just isn’t going to work. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for the feedback on this, by the way! I really appreciate it!<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Joel<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> support-bounces@drupal.org [mailto:support-bounces@drupal.org] <b>On Behalf Of </b>Ms. Nancy Wichmann<br><b>Sent:</b> Thursday, April 28, 2011 6:25 PM<br><b>To:</b> support@drupal.org<br><b>Subject:</b> Re: [support] General Drupal question<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Scaling? How many people are going to use this? It doesn't sound like many; budgets are not generally open to the world, unless it's a government site. So, I supect the first design point is to determine your target audience and how many they might be.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Secondly, it's not content types that are the issue; it's nodereferences that are. It might be that you find that some of that is not needed. For example, departmental structure is generally not very fluid, so hand-coding the department names as a list in the content type might reduce the level of performance issues considerably.<br> <o:p></o:p></p></div><p><strong><i><span style='font-size:13.5pt;font-family:"Bookman Old Style","serif";color:#FF007F'>Nancy</span></i></strong><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p><p><span style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p><span style='font-family:"Arial","sans-serif"'>Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.<o:p></o:p></span></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><hr size=1 width="100%" align=center></div></div><div><p class=MsoNormal><b>From:</b> Joel Willers<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>I have a site that I’m working on the data structure for… I feel like I know how I’d do it, but I was told that it might not scale well, so I thought I’d run it through you guys. <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Would this cause too much server load using inherent Drupal Content Types with CCK fields (D6)? Would it only work with direct db queries and mysql tables instead? How much is lost doing it using content types instead of custom coding? <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p></div></div></div></div></body></html>