<?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 Search Indexing Memory Limit Reached! in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/search-indexing-memory-limit-reached/m-p/1519026#M86838</link>
    <description>&lt;P&gt;Hi, We're trying to index a network drive, thousands of large and complicated files.&amp;nbsp; The indexer keep quitting every 10 mins with a memory limit reached error?&amp;nbsp; Any idea how to increase the memory limit?&lt;/P&gt;&lt;P&gt;Its running on a Windows machine, Intel Xeon Processor 2.29GHx, 100 GB RAM; the indexerer is ran from an empy project file, and the process(es) never get more than a few hundred meg.&amp;nbsp; The log file is set to 2000MB file. The index files are only 6MB in size, the log and process files 27 mb.&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;</description>
    <pubDate>Tue, 13 Aug 2024 08:55:22 GMT</pubDate>
    <dc:creator>RobDunfey</dc:creator>
    <dc:date>2024-08-13T08:55:22Z</dc:date>
    <item>
      <title>Search Indexing Memory Limit Reached!</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/search-indexing-memory-limit-reached/m-p/1519026#M86838</link>
      <description>&lt;P&gt;Hi, We're trying to index a network drive, thousands of large and complicated files.&amp;nbsp; The indexer keep quitting every 10 mins with a memory limit reached error?&amp;nbsp; Any idea how to increase the memory limit?&lt;/P&gt;&lt;P&gt;Its running on a Windows machine, Intel Xeon Processor 2.29GHx, 100 GB RAM; the indexerer is ran from an empy project file, and the process(es) never get more than a few hundred meg.&amp;nbsp; The log file is set to 2000MB file. The index files are only 6MB in size, the log and process files 27 mb.&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 08:55:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/search-indexing-memory-limit-reached/m-p/1519026#M86838</guid>
      <dc:creator>RobDunfey</dc:creator>
      <dc:date>2024-08-13T08:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: Search Indexing Memory Limit Reached!</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/search-indexing-memory-limit-reached/m-p/1520660#M86920</link>
      <description>&lt;P&gt;From skimming the help page on Indexing (&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/projects/update-the-search-index-for-project-items.htm" target="_blank"&gt;https://pro.arcgis.com/en/pro-app/latest/help/projects/update-the-search-index-for-project-items.htm&lt;/A&gt;), it looks like it&amp;nbsp;&lt;EM&gt;should&lt;/EM&gt; be able to pause &amp;amp; resume, even when it hits the memory limit, I think?&lt;/P&gt;&lt;P&gt;So I guess dumb question first: Each time it stops and you restart, are you sure that it's starting from scratch, or is it resuming its progress and getting further each time?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another thought would be whether the specs on the networked drive (or the network connection, itself) might be the bottleneck.&amp;nbsp; Because the specs on your end theoretically shouldn't be a bottleneck, unless Pro isn't using all of the available resources.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm kinda surprised I haven't found anything on this page about increasing the allocated memory, but it might be there and I just haven't found it.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 16:09:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/search-indexing-memory-limit-reached/m-p/1520660#M86920</guid>
      <dc:creator>MErikReedAugusta</dc:creator>
      <dc:date>2024-08-13T16:09:49Z</dc:date>
    </item>
  </channel>
</rss>

