<?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 Re: We need to speed up getting items to staging (WCM scaleing) in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/we-need-to-speed-up-getting-items-to-staging-wcm-scaleing/m-p/229050#M182180</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi there.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What hardware is your alfresco/solaris running on? Certain Sparc hardware architectures may experience a massive slow-down. Try running on a similarly powered Intel architecture and compare your two performance benchmarks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We definitely experience much better performance issuing batches of submissions (somewhere between 50 to 100).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, all the workflows do run in a sequential serial fashion, to ensure non-concurrent mutable operations to any one sandbox. You can change also the polling frequency that this JBPM thread executes (I think it may have changed from 2 mins to 30 secs or something recently - I'd need to check)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would recommend loading up a new temporary sandbox with a batch of files, and then submitting it to the workflow, which destroys it once it has finished the merge with the staging sandbox. Immediately after triggering the submission, you're safe to create another temporary sandbox, start filling that one with new files (or changes), so that process of loading batches can be performed in parallel.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Other performance tips:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Switch off metadata extraction on your target ASR (if you happen to use either).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Keep you folder structure heavily segmented (not too many files in any one folder-node).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Operate your search webscripts as 'System' to bypass securty checks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Tom&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://www.ixxus.com" rel="nofollow noopener noreferrer"&gt;http://www.ixxus.com&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 May 2010 09:37:54 GMT</pubDate>
    <dc:creator>tommorris</dc:creator>
    <dc:date>2010-05-05T09:37:54Z</dc:date>
    <item>
      <title>We need to speed up getting items to staging (WCM scaleing)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/we-need-to-speed-up-getting-items-to-staging-wcm-scaleing/m-p/229049#M182179</link>
      <description>We have opened a ticket on this, but wanted to ask the Alfresco user community what they do in similar circumstances.The short of it is that workflows are taking longer and longer to execute after adding just a few hundred content items or having more than 3 or so users adding content and submitting</description>
      <pubDate>Fri, 19 Mar 2010 10:47:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/we-need-to-speed-up-getting-items-to-staging-wcm-scaleing/m-p/229049#M182179</guid>
      <dc:creator>kmartino</dc:creator>
      <dc:date>2010-03-19T10:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: We need to speed up getting items to staging (WCM scaleing)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/we-need-to-speed-up-getting-items-to-staging-wcm-scaleing/m-p/229050#M182180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi there.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What hardware is your alfresco/solaris running on? Certain Sparc hardware architectures may experience a massive slow-down. Try running on a similarly powered Intel architecture and compare your two performance benchmarks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We definitely experience much better performance issuing batches of submissions (somewhere between 50 to 100).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, all the workflows do run in a sequential serial fashion, to ensure non-concurrent mutable operations to any one sandbox. You can change also the polling frequency that this JBPM thread executes (I think it may have changed from 2 mins to 30 secs or something recently - I'd need to check)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would recommend loading up a new temporary sandbox with a batch of files, and then submitting it to the workflow, which destroys it once it has finished the merge with the staging sandbox. Immediately after triggering the submission, you're safe to create another temporary sandbox, start filling that one with new files (or changes), so that process of loading batches can be performed in parallel.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Other performance tips:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Switch off metadata extraction on your target ASR (if you happen to use either).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Keep you folder structure heavily segmented (not too many files in any one folder-node).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Operate your search webscripts as 'System' to bypass securty checks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Tom&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://www.ixxus.com" rel="nofollow noopener noreferrer"&gt;http://www.ixxus.com&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 May 2010 09:37:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/we-need-to-speed-up-getting-items-to-staging-wcm-scaleing/m-p/229050#M182180</guid>
      <dc:creator>tommorris</dc:creator>
      <dc:date>2010-05-05T09:37:54Z</dc:date>
    </item>
  </channel>
</rss>

