title: WPF render slower with more processors
body: <p>I'm really at a loss on this one.  I have an expander that contains an ItemsControl that looks something like this;</p>
  
  <pre><code>&lt;ItemsControl ItemsSource="{Binding Source={StaticResource SomeItems}}"&gt;
     &lt;ItemsControl.ItemTemplate&gt;                                
        &lt;DataTemplate&gt;
           &lt;StackPanel&gt;
              &lt;ContentControl Content="{Binding}" /&gt;
           &lt;/StackPanel&gt;
        &lt;/DataTemplate&gt;
     &lt;/ItemsControl.ItemTemplate&gt;                                
  &lt;/ItemsControl&gt;
  </code></pre>
  
  <p>This renders just fine when expanding on most machines (single and dual core).  For some reason when running on a brand new machine with a quad core (i7) expanding this expander takes into the minutes.  I did some profiling and it seems there are thread synchronization issues when WPF is measuring the elements, actual time spend measuring and render seem negligible, time spend waiting for thread synchronization is the bulk of it.  Has anyone else seen anything like this?</p>
  
  <p>FYI - I did attempt this on three different quad core (i7) machines and have the same issue.  No problems running on many older machines.  I confirmed that the machines are fully patched and that WPF is using hardware rendering.  Have done the obligatory application and framework re-install.</p>
  
  <p>Any ideas where else to look?</p>
  
  <p>Thanks</p>
  
  <p>--some updates from comments--</p>
  
  <p>-once the expander has been expanded, collapsing and re-expanding are fast on the problem machines</p>
  
  <p>-even when hardware rendering is disabled behavior is the same. I think that should remove the graphics card from the equation.</p>
  
  <p>-We are running .Net 4.0</p>
  
  <p>--Some Specs as requested--
  Win XP SP 3
  on
  Intel Core i7 (4 cores)
  M 620 @ 2.67GHZ
  2.98 GB of RAM
  275 GB available storage</p>