From 7d37326da8b9b9736a48216ab8e0e31a25b4a5f4 Mon Sep 17 00:00:00 2001 From: Prabhav Dogra <123436247+dograprabhav@users.noreply.github.com> Date: Wed, 27 Aug 2025 13:45:02 +0530 Subject: [PATCH 1/2] Shouldnt this be 10^12 --- content/english/hpc/complexity/languages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/english/hpc/complexity/languages.md b/content/english/hpc/complexity/languages.md index abb80979..27475839 100644 --- a/content/english/hpc/complexity/languages.md +++ b/content/english/hpc/complexity/languages.md @@ -84,7 +84,7 @@ print(duration) This code runs in 630 seconds. That's more than 10 minutes! -Let's try to put this number in perspective. The CPU that ran it has a clock frequency of 1.4GHz, meaning that it does $1.4 \cdot 10^9$ cycles per second, totaling to almost $10^{15}$ for the entire computation, and about 880 cycles per multiplication in the innermost loop. +Let's try to put this number in perspective. The CPU that ran it has a clock frequency of 1.4GHz, meaning that it does $1.4 \cdot 10^9$ cycles per second, totaling to almost $10^{12}$ for the entire computation, and about 880 cycles per multiplication in the innermost loop. This is not surprising if you consider the things that Python needs to do to figure out what the programmer meant: From b6b1c11ba1efefee5f0244c3705994d18313f81e Mon Sep 17 00:00:00 2001 From: Prabhav Dogra <123436247+dograprabhav@users.noreply.github.com> Date: Wed, 27 Aug 2025 13:47:48 +0530 Subject: [PATCH 2/2] Update languages.md --- content/english/hpc/complexity/languages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/english/hpc/complexity/languages.md b/content/english/hpc/complexity/languages.md index 27475839..6a2de09a 100644 --- a/content/english/hpc/complexity/languages.md +++ b/content/english/hpc/complexity/languages.md @@ -84,7 +84,7 @@ print(duration) This code runs in 630 seconds. That's more than 10 minutes! -Let's try to put this number in perspective. The CPU that ran it has a clock frequency of 1.4GHz, meaning that it does $1.4 \cdot 10^9$ cycles per second, totaling to almost $10^{12}$ for the entire computation, and about 880 cycles per multiplication in the innermost loop. +Let's try to put this number in perspective. The CPU that ran it has a clock frequency of 1.4GHz, meaning that it does $1.4 \cdot 10^9$ cycles per second, totaling to almost $10^{12}$ for the entire computation, and about 820 cycles per multiplication in the innermost loop. This is not surprising if you consider the things that Python needs to do to figure out what the programmer meant: