[
https://issues.apache.org/jira/browse/UNOMI-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688126#comment-17688126
]
David Griffon commented on UNOMI-741:
-------------------------------------
The current simple cache implementation has been merged as it fixes issues
introduced by the 1 second delay of ES doc indexation, 2 consecutive events for
a given session where detected as 2 different sessions whereas there should be
only one.
Next step is to improve and make the cache 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
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.
> PoC PR: [https://github.com/apache/unomi/pull/576]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
