Update cache-static-data.md taking into account cost befinit analysis… #316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… of non frequently used cached data. Signed-off-by: Jean-Phi <[email protected]>
russelltrow
added
initial review
proposed pattern
|
Hi @russelltrow , do you need anything from me? This is just a suggestion fro improvement. |
LiyaMath
requested changes
Aug 11, 2024
|
|
||
| For frequently accessed static data, especially by multiple users, consider caching on a Content Delivery Network (CDN). This reduces individual data transfers per user request, minimizing overall energy consumption. | ||
|
|
||
| If data is required multiple times for each user then caching locally might be advantageous after a propet benefit analysis. |
There was a problem hiding this comment.
Suggested change
| If data is required multiple times for each user then caching locally might be advantageous after a propet benefit analysis. | |
| If data is required multiple times for each user then caching locally might be advantageous after a proper benefit analysis. |
| Shortening the distance a network packet travels means that less energy is required to transmit it. Similarly, from an embodied carbon perspective, we are more efficient with hardware when a network packet traverses through less computing equipment. | ||
| However, a cost analysis is key. We need to compare the energy cost of data transfer with the combined cost of local storage (including its embodied carbon footprint from increased memory usage). | ||
|
|
||
| For frequently accessed static data, especially by multiple users, consider caching on a Content Delivery Network (CDN). This reduces individual data transfers per user request, minimizing overall energy consumption. |
There was a problem hiding this comment.
Suggested change
| For frequently accessed static data, especially by multiple users, consider caching on a Content Delivery Network (CDN). This reduces individual data transfers per user request, minimizing overall energy consumption. | |
| For frequently accessed static data, especially by multiple users, consider caching on a Content Delivery Network(CDN). This reduces individual data transfers per user request, minimizing overall energy consumption. |
|
|
||
| ## Solution | ||
| Caching static data, such as images or audio, instead of transferring it over the network. | ||
| Caching static data, such as videos, images or audio, instead of transferring it over the network if the cost benefit analysis proves it being more efficient. |
There was a problem hiding this comment.
Caching static data, such as videos, images, or audio, instead of transferring it over the network if the cost-benefit analysis proves it being more efficient.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… of non frequently used cached data.
Title
Update cache-static-data
Version
Designation of iteration on the pattern. This will initially be assigned by the patterns working group
Submitted By
Jean-Philippe Ulpiano
Published Date
The date this version of the pattern is published. This will be provided by the patterns working group upon approval
Intent
Caching locally is not always recommended. Different level of caching could be used according to the usage pattern.
Tags
Problem
Reduce energy and emboddied carbon caching data instead of transmitting it.
Solution
How will this patter solve the problem
SCI Impact
Caching too much useless data might lead to an increase of memeory thus leading to an increase of E.
If so much more memroy is needed, then additional might be required thus leading to more embodied carbon.
Assumptions
Caching is important but sometimes might generate trade offs.
Pros & Cons
Discussion section for pros and cons of this pattern