Garbage collection: Difference between revisions
Created page with "<html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Data Recovery Resources</title> <style> →General page styling: body { font-family: sans-serif; line-height: 1.6; } →Table of Contents (TOC) styling to match classic Wikipedia style: →format needs fixing: #toc { background-color: #f9f9f9;..." |
No edit summary |
||
| Line 128: | Line 128: | ||
<!-- background information --> | <!-- background information --> | ||
<h1> Background information </h1> | <h1> Background information </h1> | ||
<p> | <p>Garbage collection(GC) algorithms are responsible for detecting useless data such files which are simply no longer needed such as marked for deleted or unused(stale pages)(link)</br> | ||
Once the data stored within a block reaches a thread hold often defined by the GC algorithm, such as the block have a certain percentage of stale data or when the block is full.</br> | |||
The GC moves all the valid data from the block to another clear block, then clears the remaining data ready for the block to be used again </p> | |||
<h1 id="section0">What tools you will need</h1> | <h1 id="section0">What tools you will need</h1> | ||
<i> Items are not listed in any particular order </i> | <i> Items are not listed in any particular order </i> | ||
| Line 174: | Line 176: | ||
<div class="reference-list"> | <div class="reference-list"> | ||
<ol> | <ol> | ||
<li>Reference 1: <a href=" | <li>Reference 1: <a href="https://ieeexplore.ieee.org/document/6779825">Garbage Collection paper</a></li> | ||
<li>Reference 2: <a href="#">Source details</a></li> | <li>Reference 2: <a href="#">Source details</a></li> | ||
</ol> | </ol> | ||
Revision as of 15:02, 15 January 2025
Contents
Background information
Garbage collection(GC) algorithms are responsible for detecting useless data such files which are simply no longer needed such as marked for deleted or unused(stale pages)(link)
Once the data stored within a block reaches a thread hold often defined by the GC algorithm, such as the block have a certain percentage of stale data or when the block is full.
The GC moves all the valid data from the block to another clear block, then clears the remaining data ready for the block to be used again
What tools you will need
Items are not listed in any particular order
Required
- Test
Optional but useful
- Test
Uses of this skill
- 1.test
- 2.test
- 3.test
- Reference 1: Garbage Collection paper
- Reference 2: Source details
Step-by-step guide with images
Insert step-by-step walkthrough with images and summary text here
Flow chart of order of operations
Insert a flow chart of steps and actions for each task (create using diagram)
Troubleshooting/tips and tricks
Fixes to any common issues that were encountered or could be easily encountered
Related Topics
Topics such as desoldering to chip off or firmware dumping for disk PCB repairs
Further reading
External references in wiki references can just be cited through the keyword link