You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2023/02/09 15:38:00 UTC
[jira] [Updated] (UNOMI-741) Session/Event index rollover: implement sessionId/indexName affinity cache
[ https://issues.apache.org/jira/browse/UNOMI-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Jahanshahi updated UNOMI-741:
-----------------------------------
Description:
Following performance tests done on ticket: https://issues.apache.org/jira/browse/UNOMI-725
We need to implement sessionId/indexName affinity cache to speed up access to current user session on context requests.
Due to the nature of the splitted indices for the sessions it's not possible to know where exactly is stored the sessionId from the context request.
We can do a query like it is right now but as shown in the performances results test this is impact a lot the performance for concurrent context requests.
So we need to implement a sessionId/indexName affinity cache in the persistence service to speed up the loading of current user sessions.
consider a cache system with a time-to-idle feature that will automatically clean the unused sessionId after 30min and make this configurable.
was:
Following performance tests done on ticket:
We need to implement sessionId/indexName affinity cache to speed up access to current user session on context requests.
Due to the nature of the splitted indices for the sessions it's not possible to know where exactly is stored the sessionId from the context request.
We can do a query like it is right now but as shown in the performances results test this is impact a lot the performance for concurrent context requests.
So we need to implement a sessionId/indexName affinity cache in the persistence service to speed up the loading of current user sessions.
consider a cache system with a time-to-idle feature that will automatically clean the unused sessionId after 30min and make this configurable.
> Session/Event index rollover: implement sessionId/indexName affinity cache
> --------------------------------------------------------------------------
>
> Key: UNOMI-741
> URL: https://issues.apache.org/jira/browse/UNOMI-741
> Project: Apache Unomi
> Issue Type: Task
> Reporter: Kevan Jahanshahi
> Priority: Major
>
> Following performance tests done on ticket: https://issues.apache.org/jira/browse/UNOMI-725
> We need to implement sessionId/indexName affinity cache to speed up access to current user session on context requests.
> Due to the nature of the splitted indices for the sessions it's not possible to know where exactly is stored the sessionId from the context request.
> We can do a query like it is right now but as shown in the performances results test this is impact a lot the performance for concurrent context requests.
> So we need to implement a sessionId/indexName affinity cache in the persistence service to speed up the loading of current user sessions.
> consider a cache system with a time-to-idle feature that will automatically clean the unused sessionId after 30min and make this configurable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)