<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Quantity of Reserved Elements - affects file performance? in Teamwork &amp; BIMcloud</title>
    <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Quantity-of-Reserved-Elements-affects-file-performance/m-p/701254#M7655</link>
    <description>&lt;P&gt;I had an interesting report yesterday. A designer noticed that when he had all curtain walls reserved, inputting data directly into the schedule was really slow; he'd select a field, wait 10-20 seconds, input the value into the field, wait 10-20 seconds, select the next schedule cell, wait...&lt;BR /&gt;...&lt;BR /&gt;he noticed after doing a release all, and only reserving 2-3 curtain walls at a time, he was able to input data more effectively.&lt;/P&gt;
&lt;P&gt;...&lt;/P&gt;
&lt;P&gt;I've done a LOT of threshold tests, but have never noticed even reserving all affecting my file performance. Anyone else have similar experiences, or know if there may be a threshold for file performance and volume of reserved elements?&lt;BR /&gt;(for what its worth, this is a 500,000 sq ft office park, modeled to an average LOD of 300, so it's a chunky file, and we expect it to be slow in general)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Mac Apple Silicon &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Apr 2026 15:07:21 GMT</pubDate>
    <dc:creator>Patrick M</dc:creator>
    <dc:date>2026-04-30T15:07:21Z</dc:date>
    <item>
      <title>Quantity of Reserved Elements - affects file performance?</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Quantity-of-Reserved-Elements-affects-file-performance/m-p/701254#M7655</link>
      <description>&lt;P&gt;I had an interesting report yesterday. A designer noticed that when he had all curtain walls reserved, inputting data directly into the schedule was really slow; he'd select a field, wait 10-20 seconds, input the value into the field, wait 10-20 seconds, select the next schedule cell, wait...&lt;BR /&gt;...&lt;BR /&gt;he noticed after doing a release all, and only reserving 2-3 curtain walls at a time, he was able to input data more effectively.&lt;/P&gt;
&lt;P&gt;...&lt;/P&gt;
&lt;P&gt;I've done a LOT of threshold tests, but have never noticed even reserving all affecting my file performance. Anyone else have similar experiences, or know if there may be a threshold for file performance and volume of reserved elements?&lt;BR /&gt;(for what its worth, this is a 500,000 sq ft office park, modeled to an average LOD of 300, so it's a chunky file, and we expect it to be slow in general)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Mac Apple Silicon &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 15:07:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Quantity-of-Reserved-Elements-affects-file-performance/m-p/701254#M7655</guid>
      <dc:creator>Patrick M</dc:creator>
      <dc:date>2026-04-30T15:07:21Z</dc:date>
    </item>
  </channel>
</rss>

