mirrors/signal-desktop
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 2 Wiki Activity Actions

Throttle expiring messages data query and deletion

Browse source 
I believe this to be the reason behind some of the high resource usage
on startup. If a lot of read receipts come in for disappearing messages,
this method can be called many, many times very quickly.

FREEBIE
This commit is contained in:
Scott Nonnenberg 2017-08-08 09:58:44 -07:00
parent b2690afa32
commit 96b00b3e2d
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
js/expiring_messages.js
View file

@ -17,7 +17,7 @@
// the expiration before the message is removed from the database. // the expiration before the message is removed from the database.
message.destroy(); message.destroy();
}); });
expired.on('reset', checkExpiringMessages); expired.on('reset', throttledCheckExpiringMessages);
expired.fetchExpired(); expired.fetchExpired();
} }
@ -38,13 +38,14 @@
}); });
expiring.fetchNextExpiring(); expiring.fetchNextExpiring();
} }
var throttledCheckExpiringMessages = _.throttle(checkExpiringMessages, 1000);
Whisper.ExpiringMessagesListener = { Whisper.ExpiringMessagesListener = {
init: function(events) { init: function(events) {
checkExpiringMessages(); checkExpiringMessages();
events.on('timetravel', checkExpiringMessages); events.on('timetravel', throttledCheckExpiringMessages);
}, },
update: checkExpiringMessages update: throttledCheckExpiringMessages
}; };
var TimerOption = Backbone.Model.extend({ var TimerOption = Backbone.Model.extend({