Terrible performance in admin interface when activity log is of some size

kjetil commented

2015-01-29 16:54:41 +01:00

(Migrated from gitlab.lallis.org)

When accessing predi over a slowish line, it seems the websocket times out several times when first logging in as an admin. It looks like this has to do with transfering the activity log (currently about 9000 entries). On a related note, opening the activities view is slow too, but this time around it is computing the page that takes some time.

I would expect the same to show up for users once there are several thousand trades in the log.

When accessing predi over a slowish line, it seems the websocket times out several times when first logging in as an admin. It looks like this has to do with transfering the activity log (currently about 9000 entries). On a related note, opening the activities view is slow too, but this time around it is computing the page that takes some time. I would expect the same to show up for users once there are several thousand trades in the log.

kjetil commented

2015-01-29 16:55:00 +01:00

(Migrated from gitlab.lallis.org)

Currently looking into best practices for solving this at https://bulletproofmeteor.com/

kjetil commented

2015-01-29 22:25:37 +01:00

(Migrated from gitlab.lallis.org)

That article didn't really help. Turns out pagination packages for Meteor such. Looks like https://atmospherejs.com/percolate/paginated-subscription is the best bet.

kjetil commented

2015-01-29 23:11:04 +01:00

(Migrated from gitlab.lallis.org)

Still need to implement display of log entries in admin interface. Will now use one at a time collection filtered by session variable. Delayed for now to deal with more pressing issues. Leaving ticket open.

Rows
Columns

Terrible performance in admin interface when activity log is of some size #50