summaryrefslogtreecommitdiffstats
path: root/content/zettel/1f4.md
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2023-05-11 19:38:03 +0100
committerYann Herklotz <git@yannherklotz.com>2023-05-11 19:38:03 +0100
commit47c1289ff658a5aec71635d79ffe30bb29a07876 (patch)
tree56cf6b959e37fed88c492d34defd3d7ec40e7148 /content/zettel/1f4.md
parentfbe0fc62120348f582dc4db2b614078943d0764b (diff)
downloadzk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.tar.gz
zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.zip
Add content
Diffstat (limited to 'content/zettel/1f4.md')
-rw-r--r--content/zettel/1f4.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/content/zettel/1f4.md b/content/zettel/1f4.md
new file mode 100644
index 0000000..1f1184f
--- /dev/null
+++ b/content/zettel/1f4.md
@@ -0,0 +1,28 @@
++++
+title = "Complex optimisation effects"
+author = "Yann Herklotz"
+tags = []
+categories = []
+backlinks = ["1f3"]
+forwardlinks = ["1f4a"]
+zettelid = "1f4"
++++
+
+Finally, the last flakiness property that HLS tools have is that they
+apply many optimisations, which may or may not have linear effects on
+the performance and area of the result.
+
+> Because of Amdahl's law arguments, most optimizations don't have a
+> linear effect. They appear to have a linear effect sometimes, but
+> eventually hit some diminishing returns. Some other effects are really
+> discontinuous, for instance, unrolling accumulation loops may not
+> change critical recurrences. — Stephen Neuendorffer ([email])
+
+It's is nearly impossible to predict what a series of optimisations will
+do to the performance. The user will implicitly try to predict the
+performance with a simplified model as reference, and as the HLS tool
+has to take everything into account, and will therefore sometimes not be
+able to optimise the loop as the user would want it to be, leading to
+discontinuous optimisations.
+
+ [email]: notmuch:id:BYAPR02MB3910A2FA9F954031FC11A232A8479@BYAPR02MB3910.namprd02.prod.outlook.com