From version < 4.1 >
edited by Guillaume Delhumeau
on 2019/03/06 15:15
To version < 5.1 >
edited by Guillaume Delhumeau
on 2019/03/06 15:18
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  Currently, we have a big problem with notifications performances. In many cases, users are forced to disable notifications so they can simply use their wiki. The more recent example is https:~/~/jira.xwiki.org/browse/XWIKI-16207.
2 2  
3 -{{toc /}}
3 +{{toc/}}
4 4  
5 5  = Problem 1: Post-Filters can cause very long loop =
6 6  
... ... @@ -101,14 +101,10 @@
101 101  * Since the filters need to be computed for each individual user, this process can take a lot of time, and it must be performed asynchronously.
102 102  * "Event Status" are generated for users who never goes to the wikis, which is a waste of resource.
103 103  * The "Event Status" table should probably be cleaned regularly to avoid having too much data, meaning some precious notifications could be lost while a user is absent (like a 2 weeks holidays).
104 -* This mechanism cannot be applied for the Notifications Macro (that was designed to replace the Activity Stream), so it means both mechanism should co-exists.
105 -
106 -(((
107 -
104 +* **This mechanism cannot be applied for the Notifications Macro (that was designed to replace the Activity Stream), so it means both mechanism should co-exists.**
108 108  )))
109 109  )))
110 110  )))
111 -)))
112 112  
113 113  === Questions to be answered for Solution 2 - C ===
114 114  
... ... @@ -115,7 +115,8 @@
115 115  * Which store should be used to sore the "Event Status" table? Currently, it is a table in hibernate, but SOLR could be considered, or any NoSQL solution.
116 116  * Does it scale?
117 117  
118 -\\
114 += Temporary conclusion =
119 119  
116 +My favorite solution (gdelhumeau) is **2-C** because it can fix the 2 problems. But its salability needs to be tested, and it is something that will requires a lot of development, which make it difficult to do in a short period of time (especially by me) and harder to backport in 10.11.x.
120 120  
121 121  \\

Get Connected