Project

General

Profile

Task #2341

Roster management optimizations

Added by Wojciech Kapcia TigaseTeam over 4 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
4.00 h
Database:
n/a

Description

Investigate possibilities to decrease number of database I/O while performing management of roster by decreasing number of calls to saveUserRoster()

mail: Batch writing roster items

Associated revisions

Revision 33ae03ec (diff)
Added by W Administrator 4 months ago

#2341 allow specifying SubscriptionType when adding buddy to avoid calling separately .setBuddySubscription() thus eliminating saving roster twice to database if not needed

History

#1 Avatar?id=6023&size=24x24 Updated by Artur Hefczyc TigaseTeam about 4 years ago

  • Target version changed from tigase-server-7.0.0 to tigase-server-7.1.0

#2 Updated by Wojciech Kapcia TigaseTeam almost 4 years ago

  • Due date deleted (2014-10-24)

#3 Avatar?id=6023&size=24x24 Updated by Artur Hefczyc TigaseTeam over 3 years ago

  • Due date set to 2015-12-31
  • Target version changed from tigase-server-7.1.0 to tigase-server-8.0.0

#4 Updated by Wojciech Kapcia TigaseTeam about 3 years ago

  • Due date deleted (2015-12-31)

#5 Avatar?id=6023&size=24x24 Updated by Artur Hefczyc TigaseTeam almost 2 years ago

  • Parent task set to #5241

#6 Updated by Wojciech Kapcia TigaseTeam almost 2 years ago

  • Description updated (diff)
  • Start date deleted (2014-10-10)
  • Estimated time set to 4.00 h

#7 Avatar?id=6023&size=24x24 Updated by Artur Hefczyc TigaseTeam 9 months ago

  • Description updated (diff)
  • Parent task deleted (#5241)

#8 Updated by Wojciech Kapcia TigaseTeam 4 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Reported issue related mostly to UserRosterManagemet* ad-hoc groovy scripts, which called in succession .addBuddy() and .setBuddySubscription() causing two calls to .saveUserRoster().
I extended .addBuddy() with subscription parameter.
Non-script usage won't see much benefit from this change due to more intricate logic regarding handling roster manipulation and handling subscription in Presence plugin.

Also available in: Atom PDF