MANAGEMENT OF CACHED DATA BASED ON USER ENGAGEMENT

• US 20140229679A1
• Filed: 02/12/2013
• Published: 08/14/2014
• Est. Priority Date: 02/12/2013
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Kacholia, Varun, Zhang, Li, Santhanam, Sriya
• Granted Patent: US 8,954,679 B2
• Time in Patent Office: Days
• US Class Current: 711/135
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A social data aggregator generates entries of action data describing actions taken by users. A portion of the entries are stored in an action cache to expedite retrieval. To store more recent or relevant entries in the action cache, entries are removed from the action cache based on engagement scores associated with the entries. An engagement score indicates a likelihood of a user requesting content interacting with a notification based on an entry. Entries having the lowest engagement scores or having engagement scores below a threshold are removed from the action cache.

Claims

1. A method comprising:

storing action data describing actions performed by one or more users of a social networking system, at least a portion of the action data stored as entries in an action cache;

receiving information about a triggering event to purge the action cache;

identifying candidate entries from the portion of the action data stored in the action cache;

determining an engagement score for each of the candidate entries, the engagement score of a candidate entry indicating a probability of a user interacting with a notification based on the candidate entry;

selecting one or more candidate entries based at least in part on the engagement scores; and

removing the selected one or more candidate entries from the action cache.

2. The method of claim 1, wherein the engagement score for a candidate entry of action data is based at least in part on prior interactions with a notification based on the candidate entry by users of the social networking system.

3. The method of claim 1, wherein the engagement score for a candidate entry of action data is based at least in part on an affinity between a user requesting a notification and an object associated with the candidate entry of action data.

4. The method of claim 1, wherein determining the engagement score for each of the candidate entries comprises:

capturing interactions with the notification based on the candidate entry by one or more users of the social networking system; and

modifying the engagement score of the candidate entry based on the captured interactions.

5. The method of claim 1, wherein the engagement scores are determined responsive to receiving the information about the triggering event.

6. The method of claim 1, wherein the trigger event comprises a number of entries of action data in the action cache reaching a threshold.

7. The method of claim 1, wherein the trigger event comprises an amount of data stored in the action cache reaching a threshold level.

8. The method of claim 1, wherein the trigger event comprises a signal generated based on a rate at which entries of action data are generated.

12. The method of claim 8, wherein determining the engagement score for each of the entries comprises:

capturing interactions with the notification based on the entry by one or more users of the social networking system; and

modifying the engagement score of the entry based on the captured interactions.

9. A method comprising:

storing action data describing actions performed by one or more users of a social networking system, at least a portion of the action data stored as entries in an action cache

receiving information about a triggering event to purge the action cache;

determining an engagement score for each of the entries in the action cache, the engagement score of an entry indicating a probability of a user interacting with a notification based on the candidate entry;

selecting one or more entries based at least in part on the engagement scores; and

removing the selected one or more entries from the action cache.

10. The method of claim 9, wherein the engagement score for an entry of action data is based at least in part on prior interactions with a notification including the entry by users of the social networking system.

11. The method of claim 9, wherein engagement score for an entry of action data is based at least in part on an affinity between a user requesting a notification and an object associated with the entry of action data.

13. The method of claim 9, wherein the engagement scores are determined responsive to receiving the information about the triggering event.

14. The method of claim 9, wherein the trigger event comprises a number of entries of action data in the action cache reaching a threshold.

15. The method of claim 9, wherein the trigger event comprises an amount of data stored in the action cache reaching a threshold level.

16. The method of claim 9, wherein the trigger event comprises a signal generated based on a rate at which entries of action data are generated.

17. A method comprising:

storing action data describing actions performed by one or more users of a social networking system, at least a portion of the action data stored as entries in an action cache

receiving information about a triggering event to purge the action cache;

applying one or more rules to the entries stored in the action cache to identify one or more candidate entries of action data;

determining an engagement score for each of the candidate entries, the engagement score of a candidate entry indicating a probability of a user interacting with a notification based on the candidate entry;

selecting one or more candidate entries based at least in part on the engagement scores; and

removing the selected one or more candidate entries from the action cache.

18. The method of claim 17, wherein applying one or more rules to the entries stored in the action cache to identify one or more candidate entries of action data comprises:

prioritizing entries stored in the action cache based on application of the one or more rules; and

identifying the one or more candidate entries based at least in part on the prioritization.