diff --git a/CSC/ex4.html b/CSC/ex4.html
index ed06a88..cee7a43 100644
--- a/CSC/ex4.html
+++ b/CSC/ex4.html
@@ -99,7 +99,7 @@
Exercise 4: Practice tuning a small application
There are some hints at the bottom.
-I suggest you start by looking afor evidence of where the program is spending unnecessary time.
+I suggest you start by looking for evidence of where the program is spending unnecessary time.
See if you can improve those places first.
There are some obvious hot spots that will help you make progress.
@@ -114,15 +114,25 @@
Exercise 4: Practice tuning a small application
How much longer should that take? How should finding the median scale with number of samples? Is that
what you observe? If not, can you find and fix the problem?
+
+On Bob's laptop, the original program scales like:
+
+Run | CPU sec |
+
---|
time ./run 500 501 | 4.6 |
+time ./run 500 101 | 16.5 |
+time ./run 500 2001 | 63.3 |
+time ./run 500 3001 | 145.0 |
+time ./run 500 4001 | 260.9 |
+
-To add some interest, we provide some historical idea of how far students at previous CSCs have
+Students at previous CSCs have
managed to push the performance:
- If "time ./run 500 1001" with the original code takes about 20 seconds or so
- then "time ./run 500 100001", our goal, takes way too long to wait for with the original code.
- Basic profiling work should get you to about 120-135 seconds for the "time ./run 500 100001" goal
- Under 100 seconds requires care, but is possible
-
- Under 40 seconds has been done
+
- Under 40 seconds has been done but requires extraordinary effort. Is that worth it?
Note that these are with one specific laptop: Since you're using your own laptop,