Performance issue with server side Shared Roster

[irek-zaripov]

With 1000 or more contacts in roster we over-watch that the method fetch() in the string https://github.com/jcbrand/converse.js/blob/master/converse.js#L2603
converse.rosterview.render().fetch().update();
is executed a long time(more than 15 seconds) and this is inadmissible for production systems.
Further investigation shows the dependency of this issue from the https://github.com/jashkenas/backbone project.
It seems to be related to the issue jashkenas/backbone#3242 Poor "add" performance on sorted collections.
@jcbrand what do you think, what options are exist for performance optimization on fetch() method for converse.rosterview?

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[irek-zaripov]

@jcbrand What do you think about using "Nested Roster Groups" http://www.xmpp.org/extensions/xep-0083.html?
It would be a very nice feature and may be will a workaround for large roster contacts.

[jcbrand]

what do you think, what options are exist for performance optimization on fetch() method for converse.rosterview?

Looking at the ticket, I think what is happening is that roster items are fetched one by one from sessionStorage and then sorting happens every time after such a fetch.

So a good optimization would be to fetch the roster items in a batch. If this is the case, then the change would most likely have to be made in Backbone.sessionStorage.

What do you think about using "Nested Roster Groups"

This was already requested in #265. This feature is not planned for the near future, but I'm available for contracting for any new features to converse.js.

[jcbrand]

Looking at the ticket, I think what is happening is that roster items are fetched one by one from sessionStorage and then sorting happens every time after such a fetch.

This isn't the case anymore. Closing.