Last modified by Vincent Massol on 2024/02/26 17:53

<
From version < 7.1 >
edited by Guillaume Delhumeau
on 2019/03/06 15:21
To version < 8.3 >
edited by Vincent Massol
on 2019/03/06 15:27
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.gdelhumeau
1 +xwiki:XWiki.VincentMassol
Content
... ... @@ -53,7 +53,7 @@
53 53  * it does not really fix the issue. It just hides it.
54 54  
55 55  (((
56 -== Solution 2 - B: Create a thread pool for the notifications queries ==
56 +== Solution 1 - B: Create a thread pool for the notifications queries ==
57 57  
58 58  With a minor priority, these queries would be executed without slowing down the wiki. However, it does not speed up the queries themselves.
59 59  )))
... ... @@ -83,7 +83,7 @@
83 83  
84 84  1. An event is triggered in XWiki.
85 85  1. The event is recorded in the Event Stream table.
86 -1. For each user, we compute either or not the event should be displayed, according to their preferences.
86 +1. For each user, we compute either or not the event should be displayed, according to her preferences.
87 87  11. If the event should be displayed for the user, create a line in the "Event Status" table for the user, with the "read" value to false.
88 88  11. If the event should not be displayed for the user, it is simply dismissed.
89 89  1. When the user fetch the notifications, there is no complex SQL query to perform anymore. We just need to look into the "Event Status" table which events are linked to the current user id.
XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.VincentMassol
Comment
... ... @@ -1,0 +1,2 @@
1 +Things to check:
2 +* How long does it take to perform 200K writes (this is what would happen for a wiki with 200K users when everyone is subscribed to the right events and a page is modified for ex)?
Date
... ... @@ -1,0 +1,1 @@
1 +2019-03-06 15:24:56.0

Get Connected