We Do · Could This Class Run Its Own AI?

The Word Load, and What It Actually Does

There is a word this room has been using and it is doing more damage than the material it appears in. The word is load. It is used by every guide, every application, every setup instruction, every progress bar that has ever crossed a screen while a model is opening. And most of what a person thinks when they see the word is wrong.

The word sounds like moving. Load the truck. Load the dishwasher. Load the file. The English of it points at picking a thing up in one place and putting it down in another, and the place it came from is now empty because the thing is no longer there.

That is not what happens.

When a machine loads the model file, the file in storage does not go anywhere. It stays exactly where it was, at its full 6.63 gigabytes, and if the power were cut the next second the file would still be there when the machine came back on. What happens instead is a second version of the file appears in VRAM, on the card, and the machine begins reading from that second version. Same file, two addresses. The picture with the wrong drawing beside the right drawing is on the panel today because saying this in words is not enough. The wrong drawing has an arrow leaving storage and a dashed outline where the file used to be. That is the mental picture the word load produces on its own. The right drawing has no arrow at all. The file is drawn twice, once in each place, both intact.

Two things follow from this that are worth stating plainly.

The first is that VRAM has to be large enough to hold the file even though storage already is. This is why the ladder settled the question the way it did. The Chromebook has enough storage to hold this file if it had nothing else on it, and it still fails, because storage holding a copy is not what the arithmetic requires. VRAM has to hold its own copy while the machine works on it. There are two capacities in play, not one, and the numbers can differ by a factor of eight in ordinary hardware.

The second is that pulling the power out of the wall does not destroy the file. It destroys the copy. VRAM empties completely the instant the power stops, which is the reason the machine has to load the file again the next time it wants to run the model. Storage does not do that. Storage is what non-volatile means. The file will still be there at full strength the next time the machine turns on, and this is what makes loading a repeatable step rather than a permanent one.

There is one more piece the wrong picture obscures. When the model file gets larger than the card can hold, some machines will run it anyway by leaving part of the file in RAM and fetching pieces of it across a narrow connection each time they are needed. This works and it is not fast. The speed penalty is somewhere between five and thirty times slower than a file that fits on the card. That penalty exists precisely because the file is now in two active places at once, and the second place is much further from the GPU than VRAM is.

So the word load hides a shape that is nothing like the word. A copy appears. Nothing leaves. Everything stays. The file is in two places at once and one of them is not doing arithmetic on it. The picture drawn wrong on purpose is on the panel because until the room can see the wrong picture and the right picture at the same time, the word will keep pulling the mental model back to the wrong shape.

Every question on this half of the classwork asks about that difference in a different way. If a student can answer them from the shape rather than from the word, the day landed.

The diagrams · 1 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Inside the machine — RAM and CPU on the machine side, VRAM and GPU on the card, storage underneath both.

On the formthe first diagram

A machine has two of each, and the reason is that holding something and working on something are two different jobs.

Read the picture across, not down. The top row is the two places a file can sit while it is being used. The bottom row is the two things that can do the arithmetic. The left column is in the machine itself. The right column is on the card.

Storage runs underneath both columns because it belongs to neither. Nothing is ever worked on in storage. A file there is a file waiting.

The words in the boxes are the words you will see on a spec sheet, in a store, and in every guide about this you ever read.

Arc: capacity. This is the vocabulary picture. Every word this unit uses is on it. If a student can name the five boxes cold, they can read a spec sheet.

The diagrams · 2 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

At rest and in use — the same file drawn in storage, then a copy in VRAM. Same file, two addresses. One of them forgets.

On the formthe second diagram

This is one machine drawn twice, at two different moments.

On the left the file is in storage. It will survive the power going off, the machine sitting in a drawer, and a year passing. Nothing is happening to it.

On the right the same file is in VRAM. Now it can be worked on. It also disappears completely the instant the power is cut, and it has to be put there again the next time.

There is deliberately no arrow between the two halves, because nothing travelled. Both pictures are true of the same machine at different times. The file did not go on a journey. It changed address.

Arc: load means copy, not move. Same file, two addresses, both present at once. The absence of an arrow between the two halves is the point. Nothing travelled.

The diagrams · 3 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

What the word load sounds like, beside what the machine actually does. The left panel is drawn wrong on purpose.

On the formthe load misconception diagram

Two pictures of the same machine.

The picture on the left is deliberately wrong. It shows what the word load sounds like: an arrow carries the file up out of storage into VRAM, and there is a dashed outline where the file used to be.

The picture on the right is what actually happens. The file stays in storage, at full strength. A copy of it appears in VRAM. Two addresses, one file, and one of them forgets when the power goes off.

Load means copy, not move. Placed here on purpose, in grey and dashed, so the correct picture beside it has something to be correct against.

Arc: load means copy, not move. This is the drill picture. The left panel is the wrong mental model that the word load produces on its own. The right panel is the shape the machine actually uses. The only way to unlearn the wrong picture is to see it beside the right one.

The diagrams · 4 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Will it fit? Panel 1 of the ladder — Chromebook, 4 GB RAM against a 6.63 GB file.

On the formbuilds up to the third diagram

Every bar is drawn to the same scale, and the red block is the same file every time. That is what makes the four comparisons honest.

The question is the same for each machine and it is answered with subtraction. Is the number on the machine larger than 6.63, or is it not.

The first bar is different from the other three, and the difference matters. The Chromebook’s bar is RAM, the working memory in the machine itself. The other three bars are VRAM, working memory on a card. The Chromebook does not have a small card. It has no card at all, which is why its RAM is the only thing that could possibly hold the file, and why it comes up short by 2.63 gigabytes.

Notice what the question never needed. Not the speed of the machine, not the year it was made, not the price. One subtraction settled all four.

Three machines in the world can hold this file. None of them is in this room.

Arc: capacity. Four machines, one file, one subtraction. Three cards can hold it. None of them is in this room. The Chromebook’s bar is RAM because it has no card at all, which is why 4 gigabytes is what it can offer and why it comes up short by 2.63.

The diagrams · 5 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Will it fit? Panel 2 — RTX 4060, 8 GB VRAM.

On the formbuilds up to the third diagram

Every bar is drawn to the same scale, and the red block is the same file every time. That is what makes the four comparisons honest.

The question is the same for each machine and it is answered with subtraction. Is the number on the machine larger than 6.63, or is it not.

Notice what the question never needed. Not the speed of the machine, not the year it was made, not the price. One subtraction settled all four.

Three machines in the world can hold this file. None of them is in this room.

The diagrams · 6 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Will it fit? Panel 3 — RTX 5070 Ti, 16 GB VRAM.

On the formbuilds up to the third diagram

Every bar is drawn to the same scale, and the red block is the same file every time. That is what makes the four comparisons honest.

The question is the same for each machine and it is answered with subtraction. Is the number on the machine larger than 6.63, or is it not.

Notice what the question never needed. Not the speed of the machine, not the year it was made, not the price. One subtraction settled all four.

Three machines in the world can hold this file. None of them is in this room.

The diagrams · 7 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Will it fit? Panel 4 — RTX 4090, 24 GB VRAM.

On the formbuilds up to the third diagram

Every bar is drawn to the same scale, and the red block is the same file every time. That is what makes the four comparisons honest.

The question is the same for each machine and it is answered with subtraction. Is the number on the machine larger than 6.63, or is it not.

Notice what the question never needed. Not the speed of the machine, not the year it was made, not the price. One subtraction settled all four.

Three machines in the world can hold this file. None of them is in this room.

The diagrams · 8 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

The ladder — all four machines together, with verdicts. This is the panel students copy.

On the formthe third diagram

Every bar is drawn to the same scale, and the red block is the same file every time. That is what makes the four comparisons honest.

The question is the same for each machine and it is answered with subtraction. Is the number on the machine larger than 6.63, or is it not.

Notice what the question never needed. Not the speed of the machine, not the year it was made, not the price. One subtraction settled all four.

Three machines in the world can hold this file. None of them is in this room.

The diagrams · 9 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Numbers, not instructions — a program (readable lines) beside the model file (rows of numbers).

On the formthe first diagram

Both sides are files. Only one of them is a program.

On the left are instructions: steps a machine can carry out, in order, one after another. You do not have to understand what the program does to see that it is telling something to do something.

On the right is the model file. There are no steps. There is no order. There is nothing to carry out. It is a record of numbers, billions of them, and a machine handed this file has been given no instructions at all.

That is why yesterday ended with a file that fits on three machines and does nothing on any of them. Fitting was never the last problem.

Arc: the software stack. This picture is the bridge from Day 1 to Day 2. Yesterday’s file has no instructions. Something else has to open it, and that something is the runtime. Capacity was not the last problem.

The diagrams · 10 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

The software stack — the machine contains the OS, which contains the runtime, which holds the file. Four layers.

On the formthe software stack diagram

Four layers, each one sitting inside the one above it.

The machine is the hardware. The operating system is the software that starts when the power comes on and decides what else is allowed to run. The runtime is a real program, with real instructions in it, whose whole job is to open a file that has none. The file sits inside the runtime because the runtime is the only thing that can do anything with it.

Take any one layer away and nothing answers. That is worth testing on yourself: pick a layer, remove it, and say what breaks.

Arc: the software stack. Four layers, in the only order that lets an answer come back. Machine, operating system, runtime, file. Remove any one layer and nothing answers.

The diagrams · 11 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

Same file, same engine — LM Studio on top of llama.cpp on one side, llama.cpp alone on the other.

On the formthe two-stack diagram

Both sides are running the identical file, and both sides are running the identical engine.

llama.cpp is the engine. It is the software that actually reads the numbers and does the arithmetic. On the left, LM Studio sits on top of it as a window, so a person clicks. On the right there is no window, so a person types instead. That is the entire difference.

The file has no opinion about any of this, because the file does not know either program exists. Two things that can be swapped without touching each other were never one thing.

This is the point the rest of the unit rests on. Somebody made the file. Somebody unconnected wrote the engine. A third group built the card, aiming it at people who play video games. None of them know each other, and the thing still runs.

Arc: the software stack. The file and the engine are the same on both sides. The difference between them is how much software stands between a person and the machine. The point is the separation: the file does not know either program exists.

The diagrams · 12 of 12

The words, in plain terms

capacity

Whether a file will fit in a place that has a size.

Two numbers, one subtraction. The file has a size, every place it could sit has a size. Storage capacity, RAM capacity, VRAM capacity — same idea in three places.

In a gameThe install-size line in system requirements: what fits on the drive.

The ladder is capacity applied to four machines. Three cards hold 6.63 gigabytes; the Chromebook comes up short.

load

Copy, not move. The file stays in storage; a copy of it appears in VRAM.

Same file, two addresses. One of them forgets the moment the power is cut. The other holds through a power cut and a year. The wrong picture is on schematic 02b for exactly this reason.

In a game"Loading…" between a menu and a level. Nothing leaves the disc when the level loads; a copy of the level arrives in memory.

runtime

Software with real instructions in it, whose whole job is to open a file that has none.

In this room the runtime is LM Studio, with llama.cpp underneath. Without one, the file sits and does nothing. That is what the third failure is about.

In a gameA game engine like Unity or Unreal — the piece that reads the maps and runs the rules.

The hole — the same stack with the runtime box empty. Chromebook. Not too small, not too slow, not allowed.

On the formthe Chromebook diagram

This is the same picture as the software stack, with one box empty. Compare them directly. The machine is the same size, the operating system region is the same size, and the runtime box is in exactly the same place.

What changed is that the box is empty and cannot be filled. ChromeOS does not permit software like LM Studio or llama.cpp to be installed on a school-managed device.

The file has moved outside the machine, because there is nothing in there that could open it.

This is the Chromebook’s third failure and it is different in kind from the other two. The first was storage, and deleting things would fix it. The second was RAM, and nothing you delete would help. This one is not about a number at all. Not too small, not too slow, not allowed.

Arc: the software stack. The third failure, and the one that is not about a number. ChromeOS will not permit a runtime. Not too small, not too slow, not allowed. Buying more of anything does not change what the operating system allows.

View

The classwork

Could this class run its own AI? Day 3 of 6. Section 1 goes with the reading on your screen. Section 2 goes with the twelve diagrams from last week. Answer the required items first. If you finish those, keep going. Station view is read-only — it is the backup for a form that will not load. Switch back to My view to answer for a grade.

Question 1multiple choice

Which period are you in?

APeriod 1
BPeriod 2
CPeriod 4

Question 2multiple choice

According to the reading, what does the word load sound like it means?

ACopy something without moving it
BPick a thing up in one place and put it down in another, leaving the first place empty
CDelete a file and download it again
DRun a program without opening it

Question 3multiple choice

According to the reading, what actually happens when a machine loads the model file?

AThe file leaves storage and arrives in VRAM
BThe file is split between storage and RAM
CThe file stays in storage at full strength, and a copy of it appears in VRAM
DThe file is renamed and moved to the card

Question 4multiple choice

The reading says the picture with the wrong drawing is on the panel on purpose. What is the wrong drawing showing?

AAn arrow from storage to VRAM, with a dashed outline where the file used to be
BThe file in three places at once
CA picture of RAM with no file in it
DThe runtime with no operating system underneath it

Question 5multiple choice

Why does VRAM have to be large enough to hold the file even though storage already is?

ABecause storage and VRAM are the same thing under different names
BBecause the file has to be held in VRAM while the machine works on it, and holding a copy in storage does not remove that requirement
CBecause storage cannot hold files larger than four gigabytes
DBecause the operating system moves the file automatically

Question 6multiple choice

The reading says pulling the power out of the wall destroys the copy in VRAM but not the file in storage. What word does it use for the property storage has that VRAM does not?

AWorking memory
BNon-volatile
CCached
DNetworked

Question 7multiple choice

When a file is too large for the card, some machines run it anyway by leaving part of it in RAM and fetching pieces across a narrow connection. What does the reading say happens to the speed?

AIt stays about the same
BIt gets slightly faster because two memories are used
CIt becomes five to thirty times slower than a file that fits on the card
DIt becomes exactly half the speed

Question 8multiple choice

According to the reading, when the model file is running from VRAM alone, what is the file doing in storage?

AIt is being deleted to save space
BIt is sitting there at full strength, exactly as it was before loading
CIt is being compressed
DIt is being copied a second time

Question 9multiple choice

The reading says a copy of the file appears in VRAM. Which pair of words best names what has happened?

AMove and delete
BCopy and keep
CRename and hide
DUpload and download

Question 10multiple choice

Why did the ladder from Day 1 settle the question by comparing the file to VRAM on three cards, not to storage?

ABecause storage on those machines is always the same size
BBecause VRAM is the number that decides whether the machine can work on the file, not just hold it
CBecause storage is cheaper than VRAM
DBecause the ladder was drawn wrong on Day 1 and the reading is correcting it

Question 11multiple choice

Which sentence best states the reading’s main point?

ALoad is the wrong word and should be replaced
BThe file is in two places at once when the machine is running it, and the word load hides that shape
CVRAM is always better than RAM
DStorage is the only memory that matters

Question 12written

The reading says the wrong picture and the right picture have to be on the panel at the same time until the room can see them together. Explain in your own words what the wrong picture shows, what the right picture shows, and why one picture on its own would not be enough.

Paragraph.

Question 13written

A friend tells you they know their machine is running the model because storage is emptier now than it was before loading. Using the reading, explain what they have gotten wrong and what would actually be different on the machine while the model is running.

Paragraph.

Question 14multiple choice

On the first diagram (schematic 01, the vocabulary picture), which two things sit on the card?

ARAM and CPU
BVRAM and GPU
CStorage and RAM
DStorage and GPU

Question 15multiple choice

On the ladder (schematic 03e), how many of the four machines can hold the 6.63 gigabyte file, and which one comes up short?

AAll four; the Chromebook has the least room
BThree; the Chromebook comes up short by 2.63 gigabytes
CTwo; the 5070 Ti and the 4090 hold it
DOne; only the 4090 holds it

Question 16multiple choice

On the load-misconception diagram (schematic 02b), what tells you the picture on the left is drawn wrong on purpose?

AIt has an arrow leaving storage and a dashed outline where the file used to be
BIt has no file drawn in it
CIt has the file in three places
DIt is drawn in colour and the right picture is in grey

Question 17multiple choice

On the at-rest-and-in-use diagram (schematic 02), there is no arrow between the two halves. Why?

ABecause arrows are hard to draw
BBecause nothing travels; both pictures are true of the same machine at different times
CBecause the file is moving too fast to draw an arrow
DBecause the arrow is on schematic 02b instead

Question 18multiple choice

On schematic 02b, load means what?

AMove
BCopy
CDelete
DRename

Question 19multiple choice

On schematic 04 (numbers, not instructions), what is the difference between the two files shown?

AOne is larger than the other
BOne is a program with instructions a machine can follow; the other is a record of numbers with no instructions in it
COne is stored on a card and one is stored on a drive
DOne is finished and one is still being made

Question 20multiple choice

On the software stack (schematic 05), what sits directly around the model file?

AThe operating system
BThe machine
CStorage
DThe runtime

Question 21multiple choice

On the two-stack diagram (schematic 06), what changes between the two sides, and what stays the same?

AThe file and the engine change; the operating system stays the same
BThe file and the engine stay the same; LM Studio is on one side and not the other
CThe card changes; the file stays the same
DThe operating system changes; the file and the engine stay the same

Question 22multiple choice

On the hole diagram (schematic 07), what has changed from the software stack picture?

AThe file is larger
BThe runtime box is empty and cannot be filled, because ChromeOS will not permit a runtime to be installed
CThe operating system is missing
DThe machine is a different colour

Question 23multiple choiceoptional

On the ladder (schematic 03e), the Chromebook’s bar is labelled RAM and the other three bars are labelled VRAM. What does that difference tell you?

AThe Chromebook has a small card
BThe Chromebook has no card at all, so its RAM is the only thing that could hold the file
CVRAM and RAM are two words for the same thing
DThe Chromebook’s card is too old to be listed

Question 24multiple choiceoptional

On schematic 05, taking any one layer away leaves nothing that answers. Which of these is not one of those four layers?

AThe machine
BThe operating system
CThe runtime
DThe card manufacturer

Question 25written

Pick one of the twelve diagrams and explain, in your own words, which of the three arcs (capacity, load-means-copy, or the software stack) it belongs to and how you can tell.

Paragraph.

Question 26writtenoptional

The Chromebook fails three times, and the third failure is different in kind from the first two. Using schematic 07 and either schematic 03e or schematic 05, explain what makes the third failure different, and what a student could and could not do about it.

Paragraph.

The first item is your name. Answer it — that is what puts you on the work now that email collection is off.

Exit ticket · on your own