<?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 Scalability in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/scalability/m-p/64881#M40989</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Dear Communitity&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We are planning to use activiti for a system which processes a couple of million orders per year, thus there will be quite a lot process instances running simultaniousely. Are there any case studies or something like that which show that activiti is able to handle such loads? Is anybody aware of any scalability issues?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks a lot in advance for your feedback&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Christoph&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Oct 2011 06:30:52 GMT</pubDate>
    <dc:creator>chris889</dc:creator>
    <dc:date>2011-10-21T06:30:52Z</dc:date>
    <item>
      <title>Scalability</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/scalability/m-p/64881#M40989</link>
      <description>Dear CommunitityWe are planning to use activiti for a system which processes a couple of million orders per year, thus there will be quite a lot process instances running simultaniousely. Are there any case studies or something like that which show that activiti is able to handle such loads? Is anyb</description>
      <pubDate>Fri, 21 Oct 2011 06:30:52 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/scalability/m-p/64881#M40989</guid>
      <dc:creator>chris889</dc:creator>
      <dc:date>2011-10-21T06:30:52Z</dc:date>
    </item>
    <item>
      <title>Re: Scalability</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/scalability/m-p/64882#M40990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In a single node test for a non-trivial process, i saw the following numbers. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;These are with default configuration. I have not tried to optimize or tune anything&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Scenario - Create process instance with 4 custom POJOs, one containing a list (usually its best to have not more than 1 or 2 lightweight pojos)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Tomcat/SqlServer &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5&amp;nbsp; threads - 596/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;10&amp;nbsp; threads - 936/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;50&amp;nbsp; threads - 613/minute (server maxed out)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Was/Sqlserver&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5 thread - 1359/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;10 thread - 1701/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;50 thread -&amp;nbsp; 446/minute (server did not max out)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No exceptions in either case&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Scenario - Claim task (display 25 tasks/page; each thread claims a random task on page)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Logic - &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; get 25 tasks on a page&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; processConfig.getTaskService().createTaskQuery().processDefinitionKey(PROCESS_KEY).taskUnnassigned().listPage(0,25);&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; select a task on page at random&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; processConfig.getTaskService().claim(task.getId(), user.getId());&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Tomcat/SqlServer &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5&amp;nbsp; threads - 521/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;10 threads - 720/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;50 threads - 394/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;WAS/SqlServer&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5 threads - 202/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;10 threads - 241/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;50 threads - 181/minute&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# of exceptions were approx 10%, 20% and 50% respectively in both cases, all related to threads concurrently claiming the same task. That has more to do with process design than activiti itself&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The only 'issue' was about timers/jobs. if there were a several process instances and timers are required, it took a while to trigger escalations. I had a task escalated if noone worked on it for 15 minutes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In a multi node environment, some other posts had said to run the jobexecutor on only one node, so that may be a constraint&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Oct 2011 17:54:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/scalability/m-p/64882#M40990</guid>
      <dc:creator>mahavirj</dc:creator>
      <dc:date>2011-10-28T17:54:07Z</dc:date>
    </item>
  </channel>
</rss>

