# How would you memorize material like this?

**URL:** <https://forum.artofmemory.com/t/how-would-you-memorize-material-like-this/103542>\
**Category:** Homework and Study Help\
**Tags:** comptia\
**Created:** [July 2, 2025, 3:11pm UTC](https://forum.artofmemory.com/t/how-would-you-memorize-material-like-this/103542 "2025-07-02T15:11:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LoneSpirit\_afm](https://forum.artofmemory.com/letter_avatar_proxy/v4/letter/l/ebca7d/32.png) [@LoneSpirit\_afm](https://forum.artofmemory.com/u/LoneSpirit_afm)\
**Post date:** [July 2, 2025, 3:11pm UTC](https://forum.artofmemory.com/t/how-would-you-memorize-material-like-this/103542/1 "2025-07-02T15:11:38Z")

</div>

Hey, I’m currently studying for the CompTIA A+ exam using Mike Meyers’ book. My approach is to read through the material, eliminate the filler content, and note down everything in _ **bullet points** _. I plan to use a memory palace to help retain the information. However, I don’t use memory techniques very often, so I’d appreciate your input on how you would go about memorizing material like this.

A small part from chapter 3/CPUs:

- **Cache**  **:**
  - Because the CPU runs faster than the _ **RAM** _ can supply it with code, you’ll always get pipeline stalls called _ **wait** _ _ **states** _ because the _ **RAM** _ can’t keep up with the CPU.
  - To reduce _ **wait** _ _ **states** _, CPUs come with built-in, very high-speed _ **RAM** _ called _ **static** _ _ **RAM** _ (_ **SRAM** _).
  - The moment you double-clicked an icon, Windows started sending many programs to the CPU.
  - Each of these programs breaks down into some number of little pieces, called _threads_, and _data_. (_threads_ are a series of instructions designed to do a particular job with the _data_)
  - Most applications have certain instructions and data that get reused many times.
  - _ **SRAM** _ preloads as many instructions as possible and keeps copies of already run instructions and data in case the CPU needs to work on them again.
  - _ **SRAM** _ used in this fashion is called a _ **cache** _.
  - Motherboard makers began adding _ **caches** _, around 128 to 512 KB large, directly to the motherboards.
  - When the CPU looked for a line of code, it first went to the built-in _ **cache** _; if the code wasn’t there, the CPU went to the _ **cache** _ on the motherboard.
  - The _ **cache** _ on the CPU was called the _ **L1** _ _ **cache** _ because it was the one the CPU first tried to use.
  - The _ **cache** _ on the motherboard was called the _ **L2** _ _ **cache** _, not because it was on the motherboard, but because it was the second _ **cache** _ the CPU checked.
  - Eventually, engineers added the _ **L2** _ _ **cache** _ onto the CPU package, then eventually right onto the CPU chip.
  - Many modern CPUs include three: an _ **L1** _, an _ **L2** _, and an _ **L3** _ _ **cache** _ (Intel calls it _ **Smart** _ _ **Cache** _).
  - The _ **L1** _ _ **cache** _ was in the CPU and thus ran at the speed of the CPU, while the _ **L2** _ _ **cache** _ connected to the CPU via a tiny set of wires on the CPU package.

---

<div class="post-metadata">

**Author:** ![Natividade7](https://forum.artofmemory.com/user_avatar/forum.artofmemory.com/natividade7/32/28602_2.png) [@Natividade7](https://forum.artofmemory.com/u/Natividade7)\
**Post date:** [July 4, 2025, 1:10pm UTC](https://forum.artofmemory.com/t/how-would-you-memorize-material-like-this/103542/2 "2025-07-04T13:10:01Z")

</div>

> [@LoneSpirit\_afm](#):
>
> opinião sobre como você iria memorizar material como este.

I know it must be boring to emphasize this, but it’s good to say that **I** wouldn’t memorize this with the memory palace, I would try to understand what’s happening and as the world record holder of memorization Alberto Dell’Sola said: If you understand, you **NEVER** forget, and if you forget, it’s because you didn’t understand.

But that wasn’t your question, so let’s get to the point of how I would do it personally.

° _ **First: Understanding what’s going on is STILL necessary, but do it slowly on each topic.** _

° _ **Second: Once you understand it, you must eliminate everything that is useless from this information and summarize it in a way that maintains the information and reduces the number of words, summarize it in text.** _

_ **For example: instead of “Because the CPU runs faster than the RAM can provide code” remove words like “Because” and try to reduce it to: “The CPU runs faster than the RAM provide code”** _

° _ **Third: After that, try to turn the words into visible actions.** _  
_**Can you imagine a RAM delivering code? Digitally or physically? You can also imagine it delivering code in a fantastic way (Like a RAM delivering a list of codes for something)**_

_ **Imagine the situation, but in visible images, what we call “mnemonics”** _

° _ **From there, you can place the images in a memory palace, in order if you like.** _

That was a summary.

Some things to consider: I am Brazilian and I do not speak English fluently, so please be patient if something is written incorrectly, as I am translating using Google Translate.

Another thing: I do not know much about what you are studying, so if I got any details wrong, please forgive me.

Good luck and if you have any questions, I may be able to help you.