This documentation is for WSO2 Identity Server 5.2.0 . View documentation for the latest release.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Previously, WSO2 recommended to set the value of the pool size to 100. However, we empirically found out that a pool size of zero gives the best all-round performance.

When you set the <PoolSize> to zero, it applies to all three thread pools (AuthPersistenceTask, TokenPersistenceTask,  SessionDataPersistTask).

Make sure to set the <PoolSize> to zero in order to avoid the following.

  1. Data inconsistencies - This might occur in case one node delays to update the database, but meanwhile other nodes access data from that database.
  2. Performance issue - Suppose there is a sudden load to an extent that all the three queues, i.e., AuthPersistenceTask, TokenPersistenceTask,  SessionDataPersistTask are filled with data. If the thread pool is set to a value higher than zero, it will persist the data in the database concurrent with the size of the thread pool defined, utilizing all the database connections. This leads to other applications waiting for a database connection to complete its tasks.
Code Block
languagexml
 <SessionDataPersist>
     <Enable>true</Enable>
     <Temporary>false</Temporary>
     <PoolSize>0</PoolSize>
     <SessionDataCleanUp>
         <Enable>true</Enable>
         <CleanUpTimeout>20160</CleanUpTimeout>
         <CleanUpPeriod>1140</CleanUpPeriod>
     </SessionDataCleanUp>
     <OperationDataCleanUp>
         <Enable>true</Enable>
         <CleanUpPeriod>720</CleanUpPeriod>
     </OperationDataCleanUp>
</SessionDataPersist>

...