<?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 Performance and Data Connections Issue in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/performance-and-data-connections-issue/m-p/37947#M16020</link>
    <description>&lt;P&gt;I am trying a simple performance test of Activiti core engine 7.6.0.&lt;/P&gt;&lt;P&gt;I have created a simple process with 2 steps and creating multiple processes (1000 per second) but I am facing a issue Actviti side issue not releasing db connection. Other Api's will wait for Db connection and throw Exception (Unable to acquire JDBC connections) because actviti allocating all the connections.&lt;/P&gt;&lt;P&gt;In my testing, I found that the engine cannot scale beyond 50 concurrent threads. At 1-10 threads, it works fine. At 50 threads, I get errors almost half the time, and at larger number of threads, it just gets worse.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am using Postgres for the DB (connections 1000), and run the test on a Centos 7 machine with 8 cores, 24 GB RAM.&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Events =&amp;nbsp; disabled&lt;/LI&gt;&lt;LI&gt;History = disabled&lt;/LI&gt;&lt;LI&gt;Async Job Executor config&lt;/LI&gt;&lt;LI&gt;DB Pool config&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;spring.datasource.hikari.connectionTimeout: 100000&lt;BR /&gt;spring.datasource.hikari.idleTimeout: 600000&lt;BR /&gt;spring.datasource.hikari.maxLifetime: 1800000&lt;BR /&gt;spring.datasource.hikari.minimumIdle: 500&lt;BR /&gt;spring.datasource.hikari.maximumPoolSize: 850&lt;/P&gt;&lt;P&gt;activiti.async-executor.corePoolSize: 500&lt;BR /&gt;activiti.async-executor.maxPoolSize: 700&lt;BR /&gt;activiti.async-executor.keepAliveTime: 5000&lt;BR /&gt;activiti.async-executor.queueSize: 700&lt;BR /&gt;activiti.async-executor.maxTimerJobsPerAcquisition: 50&lt;BR /&gt;activiti.async-executor.maxAsyncJobsDuePerAcquisition: 50&lt;/P&gt;&lt;P&gt;spring.activiti.historyLevel: none&lt;BR /&gt;spring.activiti.dbHistoryUsed: "false"&lt;BR /&gt;spring.activiti.db-history-used: "false"&lt;BR /&gt;spring.activiti.history-level: NONE&lt;BR /&gt;spring.datasource.testWhileIdle: "true"&lt;BR /&gt;spring.datasource.validationQuery: SELECT 1&lt;/P&gt;</description>
    <pubDate>Thu, 06 Apr 2023 10:09:31 GMT</pubDate>
    <dc:creator>Sarbjeetsingh31</dc:creator>
    <dc:date>2023-04-06T10:09:31Z</dc:date>
    <item>
      <title>Performance and Data Connections Issue</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/performance-and-data-connections-issue/m-p/37947#M16020</link>
      <description>&lt;P&gt;I am trying a simple performance test of Activiti core engine 7.6.0.&lt;/P&gt;&lt;P&gt;I have created a simple process with 2 steps and creating multiple processes (1000 per second) but I am facing a issue Actviti side issue not releasing db connection. Other Api's will wait for Db connection and throw Exception (Unable to acquire JDBC connections) because actviti allocating all the connections.&lt;/P&gt;&lt;P&gt;In my testing, I found that the engine cannot scale beyond 50 concurrent threads. At 1-10 threads, it works fine. At 50 threads, I get errors almost half the time, and at larger number of threads, it just gets worse.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am using Postgres for the DB (connections 1000), and run the test on a Centos 7 machine with 8 cores, 24 GB RAM.&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Events =&amp;nbsp; disabled&lt;/LI&gt;&lt;LI&gt;History = disabled&lt;/LI&gt;&lt;LI&gt;Async Job Executor config&lt;/LI&gt;&lt;LI&gt;DB Pool config&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;spring.datasource.hikari.connectionTimeout: 100000&lt;BR /&gt;spring.datasource.hikari.idleTimeout: 600000&lt;BR /&gt;spring.datasource.hikari.maxLifetime: 1800000&lt;BR /&gt;spring.datasource.hikari.minimumIdle: 500&lt;BR /&gt;spring.datasource.hikari.maximumPoolSize: 850&lt;/P&gt;&lt;P&gt;activiti.async-executor.corePoolSize: 500&lt;BR /&gt;activiti.async-executor.maxPoolSize: 700&lt;BR /&gt;activiti.async-executor.keepAliveTime: 5000&lt;BR /&gt;activiti.async-executor.queueSize: 700&lt;BR /&gt;activiti.async-executor.maxTimerJobsPerAcquisition: 50&lt;BR /&gt;activiti.async-executor.maxAsyncJobsDuePerAcquisition: 50&lt;/P&gt;&lt;P&gt;spring.activiti.historyLevel: none&lt;BR /&gt;spring.activiti.dbHistoryUsed: "false"&lt;BR /&gt;spring.activiti.db-history-used: "false"&lt;BR /&gt;spring.activiti.history-level: NONE&lt;BR /&gt;spring.datasource.testWhileIdle: "true"&lt;BR /&gt;spring.datasource.validationQuery: SELECT 1&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 10:09:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/performance-and-data-connections-issue/m-p/37947#M16020</guid>
      <dc:creator>Sarbjeetsingh31</dc:creator>
      <dc:date>2023-04-06T10:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: Performance and Data Connections Issue</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/performance-and-data-connections-issue/m-p/37948#M16021</link>
      <description>&lt;P&gt;Anyone can update for the same.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Apr 2023 04:23:20 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/performance-and-data-connections-issue/m-p/37948#M16021</guid>
      <dc:creator>Sarbjeetsingh31</dc:creator>
      <dc:date>2023-04-28T04:23:20Z</dc:date>
    </item>
  </channel>
</rss>

