Dynamic storage tiering
A method for dynamic storage tiering may include, but is not limited to: receiving an input/output (I/O) request from a host device; determining whether the I/O request results in a cache hit; and relocating data associated with the I/O request between a higher-performance storage device and lower-performance storage device according to the determination whether the data associated with the I/O request is stored in a cache.
1. A method for dynamic storage tiering comprising:
receiving an input/output (I/O) request from a host device;
determining whether the I/O request results in a cache hit;
comparing at least one of a number of cache hits associated with data associated with the I/O request or a frequency of cache hits associated with data associated with the I/O request to a threshold range; and
relocating data associated with the I/O request between a higher-performance storage device and lower-performance storage device according to a comparison of at least one of a number of cache hits associated with data associated with the I/O request or a frequency of cache hits associated with data associated with the I/O request to a threshold range.
2. The method of claim 1 , wherein the data associated with the I/O request comprises logical block address (LBA)-level data.
3. The method of claim 2 ,
wherein the determining whether the I/O request results in a cache hit further comprises:
applying a weighting to a first LBA range according to cache hit data associated with the first LBA range; and
applying a weighting to a second LBA range according to cache hit data associated with the second LBA range, and
wherein the relocating data associated with the I/O request between a higher-performance storage device and lower-performance storage device according to a comparison of at least one of a number of cache hits associated with data associated with the I/O request or a frequency of cache hits associated with data associated with the I/O request to a threshold range further comprises:
relocating either the first LBA range or the second LBA range according to relative weightings of the first LBA range and the second LBA range.
4. The method of claim 3 , wherein the first LBA range is adjacent to the second LBA range.
5. The method of claim 3 , wherein a weighting is a function of at least one of: a cache hit count associated with the LBA range; a cache hit time; a cache hit frequency; or a cache hit count associated with a second LBA range adjacent to the LBA range.
6. The method of claim 1 , further comprising:
receiving a user input;
retaining data associated with the I/O request in a present storage location when at least one of a number of cache hits associated with data associated with the I/O request and a frequency of cache hits associated with data associated with the I/O is outside a user-defined threshold range.
7. The method of claim 6 , wherein the user input is indicative of a volume snapshot operation.
8. The method of claim 6 , wherein the present storage location is a lower performance storage location.
9. A system for dynamic storage tiering comprising:
means for receiving an input/output (I/O) request from a host device;
means for determining whether the I/O request results in a cache hit;
means for comparing at least one of a number of cache hits associated with data associated with the I/O request or a frequency of cache hits associated with data associated with the I/O request to a threshold range; and
means for relocating data associated with the I/O request between a higher-performance storage device and lower-performance storage device according to a comparison of at least one of a number of cache hits associated with data associated with the I/O request or a frequency of cache hits associated with data associated with the I/O request to a threshold range.
10. The system of claim 9 , wherein the data associated with the I/O request comprises logical block address (LBA)-level data.
11. The system of claim 10 ,
wherein the means for determining whether the I/O request results in a cache hit further comprises:
means for applying a weighting to a first LBA range according to cache hit data associated with the first LBA range; and
means for applying a weighting to a second LBA range according to cache hit data associated with the second LBA range, and
wherein the means for relocating data associated with the I/O request between a higher-performance storage device and lower-performance storage device according to a comparison of at least one of a number of cache hits associated with data associated with the I/O request or a frequency of cache hits associated with data associated with the I/O request to a threshold range further comprises:
means for relocating either the first LBA range or the second LBA range according to relative weightings of the first LBA range and the second LBA range.
12. The system of claim 11 , wherein the first LBA range is adjacent to the second LBA range.
13. The system of claim 11 , wherein a weighting is a function of at least one of: a cache hit count associated with the LBA range; a cache hit time; a cache hit frequency; or a cache hit count associated with a second LBA range adjacent to the LBA range.
14. The system of claim 9 , further comprising:
means for receiving a user input;
means for retaining data associated with the I/O request in a present storage location when at least one of a number of cache hits associated with data associated with the I/O request and a frequency of cache hits associated with data associated with the I/O is outside a user-defined threshold range.
15. The system of claim 14 , wherein the user input is indicative of a volume snapshot operation.
16. The system of claim 14 , wherein the present storage location is a lower performance storage location.