title: CoreData - performance when having many relationships on an Entity
body: <p>I hope this hasn't been asked before, I searched for a similar question but couldn't find something that's close enough to my case.</p>
  
  <p>Basically, my question is if CoreData can handle a big amount of relationships (by big I mean maybe up to 30 on some entities) while not being slowed down too much.</p>
  
  <p>I have these entities (Just as a demonstration):</p>
  
  <pre><code>Resources (contains all Resources for an object)
  ProcessA
  ProcessB
  ProcessC
  ProcessD
  ProcessE
  ... (many more)
  </code></pre>
  
  <p>These processes are needed for various tasks but nearly all of them need to have a to-one (or to-many) relationship to <code>Resources</code>. </p>
  
  <p>Sometimes, they even need multiple relationships to <code>Resources</code> (<code>currentResources</code> and <code>oldResources</code> or whatever). That's why I need to add an inverse relationship (it actually causes problems if I don't have inverses. I don't know why).</p>
  
  <p>Due to the inverses, the <code>Relationships</code> entity starts to look like this:</p>
  
  <pre><code>Resources
     someAttribute
     ...
     ---
  -&gt; inverseOfProcessA
  -&gt; inverseOfProcessB
  -&gt; inverseOfProcessC
  -&gt; inverseOfProcessD
  -&gt; inverseOfProcessE
  -&gt; ...
  </code></pre>
  
  <p>It's getting filled with inverse relationships that I will never need to access from this side (they just have to be there to prevent some strange things from happening).</p>
  
  <p>I read into the concept of <code>faulting</code>. Is my understanding correct that when I fetch a <code>Resources</code> object, it doesn't actually load all the relationships? If so, how efficient is <code>faulting</code>? Because it does have to fill all of the relationships with <code>fault</code>-objects. That's the part I'm not really sure about. Does this impact performance when having many relationships on an entity?</p>
  
  <hr>
  
  <p>I am sorry if this is a trivial question. The answer might be obvious, but I've just started worrying about performance and this interests me (and even though I read about <code>faults</code> in the documentation, this is not 100% clear to me)</p>