Systems and methods for birth time-based FIFO cache reaping

1 . A computer-implemented method for cache management comprising:

obtaining, via one or more processors, an object to be stored in a cache;

storing, via the one or more processors, the object in the cache such that the object is associated with a birth time at which the storage occurred, wherein the birth time is constant as changes to the object are synchronized to the cache;

calculating, via one or more processors, a cache storage time for the object based on the birth time for the object;

determining, via the one or more processors, that the cache storage time for the object exceeds a maximum cache storage threshold;

responsive to the determination, flagging, via the one or more processors, the object for deletion from the cache; and

responsive to determining, via the one or more processors, that the object flagged for deletion has pending writes to a long-term storage (LTS) system, queueing, via the one or more processors, the pending writes for synchronization with the LTS system.

2 . The computer-implemented method of claim 1 , wherein determining that the object flagged for deletion has the pending writes to the LTS system comprises:

determining, via the one or more processors, a value for a write flag associated with the object.

3 . The computer-implemented method of claim 1 , wherein determining that the object exceeds the maximum cache storage threshold comprises:

periodically comparing, via the one or more processors, the cache storage time to the maximum cache storage threshold.

4 . The computer-implemented method of claim 1 , wherein determining that the object exceeds the maximum cache storage threshold comprises:

determining, via the one or more processors, an activity level associated with the cache; and

comparing, via the one or more processors, the cache storage time to the maximum cache storage threshold when the activity level is below a threshold activity level.

5 . The computer-implemented method of claim 1 , further comprising:

detecting, via the one or more processors, a user input defining the maximum cache storage threshold.

6 . The computer-implemented method of claim 1 , wherein associating the object with the birth time comprises:

storing, via the one or more processors, the birth time in object metadata in the cache.

7 . The computer-implemented method of claim 1 , wherein associating the object with the birth time comprises:

modifying, via the one or more processors, the object to indicate the birth time.

8 . The computer-implemented method of claim 1 , further comprising:

causing, via the one or more processors, the object flagged for deletion to be deleted from the cache.

9 . The computer-implemented method of claim 1 , further comprising:

receiving, via the one or more processors, one or more modifications to the object; and

maintaining, via the one or more processors, the birth time as unchanged.

10 . A cache management system comprising:

a cache;

one or more processors; and

one or more non-transitory memories coupled to the one or more processors and storing instructions that when executed by the one or more processors, cause the one or more processors to:

obtain an object to be stored in a cache;

store the object in the cache such that the object is associated with a birth time at which the storage occurred, wherein the birth time is constant as changes to the object are synchronized to the cache;

calculate a cache storage time for the object based on the birth time for the object;

determine that the cache storage time for the object exceeds a maximum cache storage threshold;

responsive to the determination, flag the object for deletion from the cache; and

responsive to determining that the object flagged for deletion has pending writes to a long-term storage (LTS) system, queue the pending writes for synchronization with the LTS system.

11 . The cache management system of claim 10 , wherein determining that the object flagged for deletion has the pending writes to the LTS system comprises:

determining a value for a write flag associated with the object.

12 . The cache management system of claim 10 , wherein determining that the object exceeds the maximum cache storage threshold comprises:

periodically comparing the cache storage time to the maximum cache storage threshold.

13 . The cache management system of claim 10 , wherein determining that the object exceeds the maximum cache storage threshold comprises:

determining an activity level associated with the cache; and

comparing the cache storage time to the maximum cache storage threshold when the activity level is below a threshold activity level.

14 . The cache management system of claim 10 , wherein the instructions further cause the one or more processors to:

detect a user input defining the maximum cache storage threshold.

15 . The cache management system of claim 10 , wherein associating the object with the birth time comprises:

storing the birth time in object metadata in the cache.

16 . The cache management system of claim 10 , wherein associating the object with the birth time comprises:

modifying, via the one or more processors, the object to indicate the birth time.

17 . The cache management system of claim 10 , wherein the instructions further cause the one or more processors to:

cause the object flagged for deletion to be deleted from the cache.

18 . The cache management system of claim 10 , wherein the instructions further cause the one or more processors to:

receive one or more modifications to the object; and

maintain the birth time as the time at which the storage occurred.