ASPP/2024-heraklion-comp-arch
9
0
Fork 17
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

fixed links

Browse source
This commit is contained in:
Tiziano Zito 2024-08-13 14:36:22 +02:00
parent 500dafacf5
commit 2e7d5a512f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -2,7 +2,7 @@
**Important**: these are instructor notes, remove this file before showing the materials to the students. The notes can be added after the lecture, of course. **Important**: these are instructor notes, remove this file before showing the materials to the students. The notes can be added after the lecture, of course.
## Introduction ## Introduction
- [Puzzle](/puzzle.ipynb) ➔ [read-only rendered notebook](https://nbviewer.org/urls/git.aspp.school/ASPP/2024-heraklion-comp-arch/raw/branch/main/puzzle.ipynb) - [Puzzle](puzzle.ipynb) ➔ [read-only rendered notebook](https://nbviewer.org/urls/git.aspp.school/ASPP/2024-heraklion-comp-arch/raw/branch/main/puzzle.ipynb)
- Question: how come that swapping dimensions in a for-loop makes out for a huge slowdown? - Question: how come that swapping dimensions in a for-loop makes out for a huge slowdown?
- Let students play around with the notebook and try to find the "bug" - Let students play around with the notebook and try to find the "bug"
- A more thorough [benchmark](benchmark_python/) - A more thorough [benchmark](benchmark_python/)
@ -60,7 +60,7 @@ Setup:
## Back to the Python benchmark (third try) ## Back to the Python benchmark (third try)
- can we explain what is happening now? Yes, more or less ;-) - can we explain what is happening now? Yes, more or less ;-)
- quick fix for the [puzzle](/puzzle.ipynb): try and add `order='F'` in the "bad" snippet and see that is "fixes" the bug ➔ why? - quick fix for the [puzzle](puzzle.ipynb): try and add `order='F'` in the "bad" snippet and see that is "fixes" the bug ➔ why?
Notes on the [Python benchmark](benchmark_python/): Notes on the [Python benchmark](benchmark_python/):
- while running it attached to the P-core (`cpu0`), the P-core was running under a constant load of 100% (almost completely user-time) and at a fixed frequency of 3.8 GHz, where the theoretical max would be 5.2 GHz - while running it attached to the P-core (`cpu0`), the P-core was running under a constant load of 100% (almost completely user-time) and at a fixed frequency of 3.8 GHz, where the theoretical max would be 5.2 GHz