Technical Appendix

[Robadob]

Items to move across

• dis
• Hardware memory/caching
  • Rename episode (something to do with latencies?
  • Review remaining sections to make sure they're not dependent on removed content
    • I've tweaked content, (not 100% happy about the short L1 explanation, during latency overview, feels out of place)
• Hashing data structures linear-probing (ICR made tweaks to this content)
• O-notation (this requires some new content writing, in addition to what was added in the ICR PR)

I'm not to fussed about the order, they're mostly in the order of ease handling them.

Closes #61

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/RSE-Sheffield/pando-python/compare/md-outputs..md-outputs-PR-79

The following changes were observed in the rendered markdown documents:

 acknowledgements.md                               |   6 +-
 config.yaml                                       |   3 +-
 md5sum.txt                                        |  13 +-
 optimisation-conclusion.md                        |   5 +-
 optimisation-data-structures-algorithms.md        |  22 +--
 optimisation-memory.md => optimisation-latency.md |  75 ++------
 optimisation-using-python.md                      | 128 --------------
 technical-appendix.md (new)                       | 201 ++++++++++++++++++++++
 8 files changed, 233 insertions(+), 220 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-05-10 19:34:42 +0000

[Robadob]

Moves 3 technical parts into new technical appendix and tweaks surrounding text that was dependent.

O-notation is basically wholy new content, to allow for ICRs initial draft, so lower priority and I will create a standalone issue for it. Keen to get these merged before I run the course on Thursday.

(Squash merge preferred as I've not cleaned up commit history)

[JostMigenda]

I like the “latency” name for the episode; that describes it much better!

Comments are just a bunch of minor rephrasings or typo fixes.
In a few cases, the existing phrasing wasn’t particularly wrong, but I’ve changed it to read a bit more natural; but of course that is subjective, so feel free to ignore those if you disagree.

[Robadob]

All decent suggestions.

Don't feel you can't tell me to piss off and review it myself first when there's dumb mistakes I should be catching myself. 🤦‍♂️

Happy for you to accept & squash merge.