title: Serialization with BinaryFormatter *PERFORMANCE* issues
body: <p>Background:</p>
  
  <p>I'm stuck with LARGE object graph that gets serialized into some 60MBs of file (and will grow over time).  Problem isn't file size but writing and reading times, that go up to 4 minutes on some machines.</p>
  
  <p>Plot:</p>
  
  <p>Since this represents some kind of in-memory database, I can delay-load some of it.</p>
  
  <p>Thrill:</p>
  
  <p>How to measure loading time of specific object chunks?  Do I log constructor invocations and go from there?  Any better idea?</p>
  
  <p>EDIT:</p>
  
  <p>I would rather not talk about alternatives to serializing, there are lots of posts on that subject, I would rather investigate why is it so slow and what part of the object graph is the good candidate for 'excision' and delay load.</p>