[
https://issues.apache.org/jira/browse/UNOMI-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Jahanshahi updated UNOMI-725:
-----------------------------------
Description:
Since: UNOMI-724 the sessions are now loaded using query.
This ticket need to:
* measure performance difference with previous implem that was doing a direct
load instead of query
* Take action in case of performance drawback
** Consider in memory cache system to cache the sessionID/index affinity
** Consider doing multiple get on all indices until session is found if it's
more efficient than doing a query.
Personally I do prefer a caching here if it's require and performance show a
real difference.
h2. To be done:
* new perfomance test simple using jmeter to create lot of sessions and
measure differences on contextrequest system stability thresholds.
* Depeding on results: create dedicated ticket for next steps:
** cache implem for affinity
** or other logic to load sessions if better idea is found.
was:
Since: UNOMI-724 the sessions are now loaded using query.
This ticket need to:
* measure performance difference with previous implem that was doing a direct
load instead of query
* Take action in case of performance drawback
** Consider in memory cache system to cache the sessionID/index affinity
** Consider doing multiple get on all indices until session is found if it's
more efficient than doing a query.
Personally I do prefer a caching here if it's require and performance show a
real difference.
> Session/Event index rollover: measure performance of session being loaded by
> query
> ----------------------------------------------------------------------------------
>
> Key: UNOMI-725
> URL: https://issues.apache.org/jira/browse/UNOMI-725
> Project: Apache Unomi
> Issue Type: Task
> Affects Versions: unomi-2.2.0
> Reporter: Kevan Jahanshahi
> Priority: Major
> Fix For: unomi-2.2.0
>
>
> Since: UNOMI-724 the sessions are now loaded using query.
> This ticket need to:
> * measure performance difference with previous implem that was doing a
> direct load instead of query
> * Take action in case of performance drawback
> ** Consider in memory cache system to cache the sessionID/index affinity
> ** Consider doing multiple get on all indices until session is found if it's
> more efficient than doing a query.
> Personally I do prefer a caching here if it's require and performance show a
> real difference.
> h2. To be done:
> * new perfomance test simple using jmeter to create lot of sessions and
> measure differences on contextrequest system stability thresholds.
> * Depeding on results: create dedicated ticket for next steps:
> ** cache implem for affinity
> ** or other logic to load sessions if better idea is found.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
