Skip to content

Commit

Permalink
2025-01-21-ram-data-decay-research-part2: add next step propositions
Browse files Browse the repository at this point in the history
Signed-off-by: Krystian Hebel <krystian.hebel@3mdeb.com>
  • Loading branch information
krystian-hebel committed Jan 24, 2025
1 parent 355ffdf commit 5c0194e
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions blog/content/post/2025-01-21-ram-data-decay-research-part2.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,10 @@ diagram has to be modified after a number of plots was already generated. It
also has an option to export PNG versions, something that used to be done
manually.

With these changes, together with smaller improvements to performance and user
experience, we believe that the tool is ready to use outside of our laboratory.
Refer to the README in tool's repository for build and use instructions.

## Changes to methodology

With rough idea about what to expect, we slightly modified (or rather specified
Expand Down Expand Up @@ -482,6 +486,13 @@ notable exception is 4 GB Kingston Fury KF432C16BB/4, where similar level of
memory content loss was measured after about a minute. Interestingly, such
results weren't reproduced for other DDR4 modules, even from the same vendor.

All of the series were performed once. Ideally, they should be repeated few
times for each configuration to rule out random measurement errors. This wasn't
possible partially due to variations in ambient temperature that were outside of
our control, especially over longer periods of time that were required to get
full set of data. We could also repeat some tests for different units of the
same model of memory modules.

Unlock the full potential of your hardware and secure your firmware with the
experts at 3mdeb! If you're looking to boost your product's performance and
protect it from potential security threats, our team is here to help.
Expand Down

0 comments on commit 5c0194e

Please sign in to comment.