<?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 GetElementsRelatedToZones batching provides no performance benefit — expected? in Archicad Python API</title>
    <link>https://community.graphisoft.com/t5/Archicad-Python-API/GetElementsRelatedToZones-batching-provides-no-performance/m-p/713121#M1190</link>
    <description>&lt;P&gt;I'm using GetElementsRelatedToZones (Python API) to find door/window elements connected to specific zones, as part of an automated room-adjacency detection tool.&lt;/P&gt;&lt;P&gt;The command accepts a zones list, but batching multiple zones into a single call doesn't seem to help performance. For 50 zones on one floor: a single call with all 50 zones took ~37s, while making 50 individual calls (one zone each) took ~33s — essentially the same, with identical results either way.&lt;/P&gt;&lt;P&gt;Is this expected behavior (i.e. is the cost simply proportional to the amount of data being processed, so there's nothing to gain from batching), or could the batch code path be optimized to actually provide a speedup on larger projects (hundreds of zones)?&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;Windows 25h2&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 28 Aug 2026 18:38:51 GMT</pubDate>
    <dc:creator>Bajovni1</dc:creator>
    <dc:date>2026-08-28T18:38:51Z</dc:date>
    <item>
      <title>GetElementsRelatedToZones batching provides no performance benefit — expected?</title>
      <link>https://community.graphisoft.com/t5/Archicad-Python-API/GetElementsRelatedToZones-batching-provides-no-performance/m-p/713121#M1190</link>
      <description>&lt;P&gt;I'm using GetElementsRelatedToZones (Python API) to find door/window elements connected to specific zones, as part of an automated room-adjacency detection tool.&lt;/P&gt;&lt;P&gt;The command accepts a zones list, but batching multiple zones into a single call doesn't seem to help performance. For 50 zones on one floor: a single call with all 50 zones took ~37s, while making 50 individual calls (one zone each) took ~33s — essentially the same, with identical results either way.&lt;/P&gt;&lt;P&gt;Is this expected behavior (i.e. is the cost simply proportional to the amount of data being processed, so there's nothing to gain from batching), or could the batch code path be optimized to actually provide a speedup on larger projects (hundreds of zones)?&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;Windows 25h2&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Aug 2026 18:38:51 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-Python-API/GetElementsRelatedToZones-batching-provides-no-performance/m-p/713121#M1190</guid>
      <dc:creator>Bajovni1</dc:creator>
      <dc:date>2026-08-28T18:38:51Z</dc:date>
    </item>
  </channel>
</rss>

