Activity List performance in Workspace sidebar

21 views
Skip to first unread message

Shell (Aridhia Informatics)

unread,
Apr 11, 2013, 10:28:26 AM4/11/13
to choru...@googlegroups.com
Hi guys,

We've noticed some issues with the performance of the activity list in the Workspace sidebar in our codebase.

Say we have 11 activities being displayed: It appears that these are rendered ~6 times, resulting poor browser performance for a noticeable period of time.

Ahead of deeper investigation as into why this is happening, is there a quick way we can limit the number of activities displayed (to at least reduce the impact of the issue) - perhaps in activity_list_view.js - safely?

It appears paging is no longer working too, but I suspect this is another bug we've introduced.

Kind regards,

S.

Luke Winikates

unread,
Apr 11, 2013, 12:51:26 PM4/11/13
to choru...@googlegroups.com
Hi Shell,

We looked at activity_list_view.js, and it also renders 6 times for us. The total rendering time is < 1s, so we don't see any performance degradation in the browser.

You could try commenting out the this.collection.each block in postRender, which will prevent any activities from rendering at all. If rendering is the source of your performance problem, this will confirm that for you. If not, then the repeated rendering doesn't seem to be the source of your problem.

--Luke and Gregg


--
You received this message because you are subscribed to the Google Groups "chorus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chorus-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Shell Bryson

unread,
Apr 11, 2013, 2:27:41 PM4/11/13
to choru...@googlegroups.com
I'll take another look in the morning (out of office now) but we are seeing a noticeable performance hit, especially when there are larger numbers of activity events. The degradation we're seeing is significant - and for as long as 30 seconds, enough on occasion to cause pending ajax requests to fail. The application remains unresponsive, the server appears to be idling, and you can clearly see one of Chrome's rendering processes sitting at 100% CPU (Chrome's main process doesn't appear to be busy).

I'll post the result of further investigation tomorrow.

S.
Reply all
Reply to author
Forward
0 new messages