add run time info and output info for baruch/1990

We updated `bugs.md` and `1990/baruch/README.md` to record run times
and output lines for input values from 4 to 20.
This commit is contained in:
Landon Curt Noll committed 2025-04-29 11:23:08 -07:00
1 parent dac5ee684f
commit 141a76338f
7 files changed
+111 -121

No files matched your search

BIN
View File
Binary file not shown.
Binary file not shown.
+30
View File
@@ -59,6 +59,36 @@ Use `baruch.alt` as you would `baruch`.
This program reads an integer between 4 and 99 from the `stdin`.
It is advisable to commence with relatively small integers, as the
duration and quantity of output can become substantial as the input
integer increases.
For instance, on a relatively generic computer in 2025, the following
execution times and output quantities were recorded:
```
| input | clock | user | system | lines of |
| value | time | time | time | output |
|-------|---------------------|---------------------|------------------|--------------|
| 4 | 0.001s | 0.001s | 0.001s | 11 |
| 5 | 0.002s | 0.001s | 0.002s | 61 |
| 6 | 0.002s | 0.002s | 0.002s | 29 |
| 7 | 0.003s | 0.002s | 0.002s | 321 |
| 8 | 0.003s | 0.002s | 0.003s | 829 |
| 9 | 0.006s | 0.004s | 0.006s | 3521 |
| 10 | 0.016s | 0.014s | 0.006s | 7965 |
| 11 | 0.071s | 0.068s | 0.008s | 32161 |
| 12 | 0.419s | 0.418s | 0.014s | 184601 |
| 13 | 2.589s | 2.564s | 0.075s | 1031969 |
| 14 | 16.509s | 16.457s | 0.331s | 5483941 |
| 15 | 1m 55.913s | 1m 55.173s | 2.397s | 36466945 |
| 16 | 14m 7.307s | 14m 2.427s | 16.652s | 251132705 |
| 17 | 1h 49m 37.938s | 1h 48m 59.355s | 2m 2.812s | 1724671873 |
| 18 | 14h 58m 13.506s | 14h 50m 22.572s | 14m 33.652s | 12655721857 |
| 19 | 5d 6h 9m 59.983s | 5d 5h 18m 31.147s | 2h 9m 29.490s | 99361156961 |
| 20 | 46d 9h 23m 23.095s | 46d 3h 31m 11.600s | 17h 58m 55.478s | 819612966565 |
```
**NOTE**: The original program did not have a newline at the end of the file. We
added a final newline to the file to make unpacking easy.
+25
View File
@@ -478,6 +478,31 @@ question. YMMV.</p>
<p>Use <code>baruch.alt</code> as you would <code>baruch</code>.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>This program reads an integer between 4 and 99 from the <code>stdin</code>.</p>
<p>It is advisable to commence with relatively small integers, as the
duration and quantity of output can become substantial as the input
integer increases.</p>
<p>For instance, on a relatively generic computer in 2025, the following
execution times and output quantities were recorded:</p>
<pre><code> | input | clock | user | system | lines of |
| value | time | time | time | output |
|-------|---------------------|---------------------|------------------|--------------|
| 4 | 0.001s | 0.001s | 0.001s | 11 |
| 5 | 0.002s | 0.001s | 0.002s | 61 |
| 6 | 0.002s | 0.002s | 0.002s | 29 |
| 7 | 0.003s | 0.002s | 0.002s | 321 |
| 8 | 0.003s | 0.002s | 0.003s | 829 |
| 9 | 0.006s | 0.004s | 0.006s | 3521 |
| 10 | 0.016s | 0.014s | 0.006s | 7965 |
| 11 | 0.071s | 0.068s | 0.008s | 32161 |
| 12 | 0.419s | 0.418s | 0.014s | 184601 |
| 13 | 2.589s | 2.564s | 0.075s | 1031969 |
| 14 | 16.509s | 16.457s | 0.331s | 5483941 |
| 15 | 1m 55.913s | 1m 55.173s | 2.397s | 36466945 |
| 16 | 14m 7.307s | 14m 2.427s | 16.652s | 251132705 |
| 17 | 1h 49m 37.938s | 1h 48m 59.355s | 2m 2.812s | 1724671873 |
| 18 | 14h 58m 13.506s | 14h 50m 22.572s | 14m 33.652s | 12655721857 |
| 19 | 5d 6h 9m 59.983s | 5d 5h 18m 31.147s | 2h 9m 29.490s | 99361156961 |
| 20 | 46d 9h 23m 23.095s | 46d 3h 31m 11.600s | 17h 58m 55.478s | 819612966565 |</code></pre>
<p><strong>NOTE</strong>: The original program did not have a newline at the end of the file. We
added a final newline to the file to make unpacking easy.</p>
<h2 id="authors-remarks">Authors’ remarks:</h2>
+23 -56
View File
@@ -994,62 +994,29 @@ clang but on another system and it had syntax errors.</p>
<h3 id="information-1990baruchindex.html">Information: <a href="1990/baruch/index.html">1990/baruch/index.html</a></h3>
<p>A point worth considering is that as the number passed into the program gets
bigger the number of lines of output gets substantially larger and it takes much
more time and resources to run as well. For instance:</p>
<pre><code> $ for n in $(seq 1 18); do echo &quot;$n&quot;; echo &quot;$n&quot; | time &quot;./baruch&quot; | wc -l | sed -E -e &#39;s/[[:space:]]//g&#39;; done
1
3
./baruch 0.00s user 0.00s system 5% cpu 0.115 total
2
1
./baruch 0.00s user 0.00s system 64% cpu 0.004 total
3
1
./baruch 0.00s user 0.00s system 60% cpu 0.003 total
4
11
./baruch 0.00s user 0.00s system 64% cpu 0.003 total
5
61
./baruch 0.00s user 0.00s system 66% cpu 0.003 total
6
29
./baruch 0.00s user 0.00s system 61% cpu 0.003 total
7
321
./baruch 0.00s user 0.00s system 69% cpu 0.002 total
8
829
./baruch 0.00s user 0.00s system 76% cpu 0.003 total
9
3521
./baruch 0.00s user 0.00s system 87% cpu 0.005 total
10
7965
./baruch 0.01s user 0.00s system 95% cpu 0.014 total
11
32161
./baruch 0.05s user 0.00s system 98% cpu 0.053 total
12
184601
./baruch 0.29s user 0.00s system 99% cpu 0.294 total
13
1031969
./baruch 1.78s user 0.00s system 99% cpu 1.794 total
14
5483941
./baruch 11.26s user 0.02s system 99% cpu 11.311 total
15
36466945
./baruch 79.20s user 0.15s system 99% cpu 1:19.72 total
16
251132705
./baruch 592.89s user 0.77s system 99% cpu 9:55.34 total
17
1724671873
./baruch 4535.71s user 5.25s system 99% cpu 1:15:49.76 total
18
12655721857
./baruch 37496.97s user 58.50s system 99% cpu 10:27:48.29 total</code></pre>
more time and resources to run as well.</p>
<p>For instance, on a relatively generic computer in 2025, the following execution times and
output quantities were recorded:</p>
<pre><code> | input | clock | user | system | lines of |
| value | time | time | time | output |
|-------|---------------------|---------------------|------------------|--------------|
| 4 | 0.001s | 0.001s | 0.001s | 11 |
| 5 | 0.002s | 0.001s | 0.002s | 61 |
| 6 | 0.002s | 0.002s | 0.002s | 29 |
| 7 | 0.003s | 0.002s | 0.002s | 321 |
| 8 | 0.003s | 0.002s | 0.003s | 829 |
| 9 | 0.006s | 0.004s | 0.006s | 3521 |
| 10 | 0.016s | 0.014s | 0.006s | 7965 |
| 11 | 0.071s | 0.068s | 0.008s | 32161 |
| 12 | 0.419s | 0.418s | 0.014s | 184601 |
| 13 | 2.589s | 2.564s | 0.075s | 1031969 |
| 14 | 16.509s | 16.457s | 0.331s | 5483941 |
| 15 | 1m 55.913s | 1m 55.173s | 2.397s | 36466945 |
| 16 | 14m 7.307s | 14m 2.427s | 16.652s | 251132705 |
| 17 | 1h 49m 37.938s | 1h 48m 59.355s | 2m 2.812s | 1724671873 |
| 18 | 14h 58m 13.506s | 14h 50m 22.572s | 14m 33.652s | 12655721857 |
| 19 | 5d 6h 9m 59.983s | 5d 5h 18m 31.147s | 2h 9m 29.490s | 99361156961 |
| 20 | 46d 9h 23m 23.095s | 46d 3h 31m 11.600s | 17h 58m 55.478s | 819612966565 |</code></pre>
<p>This is a feature, not a bug!</p>
<p>Jump to: <a href="#">top</a></p>
<div id="1990_jaw">
+25 -57
View File
@@ -817,64 +817,32 @@ Jump to: [top](#)
A point worth considering is that as the number passed into the program gets
bigger the number of lines of output gets substantially larger and it takes much
more time and resources to run as well. For instance:
more time and resources to run as well.
``` <!---sh-->
$ for n in $(seq 1 18); do echo "$n"; echo "$n" | time "./baruch" | wc -l | sed -E -e 's/[[:space:]]//g'; done
1
3
./baruch 0.00s user 0.00s system 5% cpu 0.115 total
2
1
./baruch 0.00s user 0.00s system 64% cpu 0.004 total
3
1
./baruch 0.00s user 0.00s system 60% cpu 0.003 total
4
11
./baruch 0.00s user 0.00s system 64% cpu 0.003 total
5
61
./baruch 0.00s user 0.00s system 66% cpu 0.003 total
6
29
./baruch 0.00s user 0.00s system 61% cpu 0.003 total
7
321
./baruch 0.00s user 0.00s system 69% cpu 0.002 total
8
829
./baruch 0.00s user 0.00s system 76% cpu 0.003 total
9
3521
./baruch 0.00s user 0.00s system 87% cpu 0.005 total
10
7965
./baruch 0.01s user 0.00s system 95% cpu 0.014 total
11
32161
./baruch 0.05s user 0.00s system 98% cpu 0.053 total
12
184601
./baruch 0.29s user 0.00s system 99% cpu 0.294 total
13
1031969
./baruch 1.78s user 0.00s system 99% cpu 1.794 total
14
5483941
./baruch 11.26s user 0.02s system 99% cpu 11.311 total
15
36466945
./baruch 79.20s user 0.15s system 99% cpu 1:19.72 total
16
251132705
./baruch 592.89s user 0.77s system 99% cpu 9:55.34 total
17
1724671873
./baruch 4535.71s user 5.25s system 99% cpu 1:15:49.76 total
18
12655721857
./baruch 37496.97s user 58.50s system 99% cpu 10:27:48.29 total
For instance, on a relatively generic computer in 2025, the following execution times and
output quantities were recorded:
```
| input | clock | user | system | lines of |
| value | time | time | time | output |
|-------|---------------------|---------------------|------------------|--------------|
| 4 | 0.001s | 0.001s | 0.001s | 11 |
| 5 | 0.002s | 0.001s | 0.002s | 61 |
| 6 | 0.002s | 0.002s | 0.002s | 29 |
| 7 | 0.003s | 0.002s | 0.002s | 321 |
| 8 | 0.003s | 0.002s | 0.003s | 829 |
| 9 | 0.006s | 0.004s | 0.006s | 3521 |
| 10 | 0.016s | 0.014s | 0.006s | 7965 |
| 11 | 0.071s | 0.068s | 0.008s | 32161 |
| 12 | 0.419s | 0.418s | 0.014s | 184601 |
| 13 | 2.589s | 2.564s | 0.075s | 1031969 |
| 14 | 16.509s | 16.457s | 0.331s | 5483941 |
| 15 | 1m 55.913s | 1m 55.173s | 2.397s | 36466945 |
| 16 | 14m 7.307s | 14m 2.427s | 16.652s | 251132705 |
| 17 | 1h 49m 37.938s | 1h 48m 59.355s | 2m 2.812s | 1724671873 |
| 18 | 14h 58m 13.506s | 14h 50m 22.572s | 14m 33.652s | 12655721857 |
| 19 | 5d 6h 9m 59.983s | 5d 5h 18m 31.147s | 2h 9m 29.490s | 99361156961 |
| 20 | 46d 9h 23m 23.095s | 46d 3h 31m 11.600s | 17h 58m 55.478s | 819612966565 |
```
This is a feature, not a bug!
+8 -8
View File
@@ -1418,11 +1418,11 @@
</url>
<url>
<loc>https://www.ioccc.org/1990/1990.tar.bz2</loc>
<lastmod>2025-04-16T20:59:19+00:00</lastmod>
<lastmod>2025-04-29T18:19:53+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/1990/baruch/1990_baruch.tar.bz2</loc>
<lastmod>2025-04-16T20:59:19+00:00</lastmod>
<lastmod>2025-04-29T18:19:26+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/1990/baruch/baruch.alt.c</loc>
@@ -1438,7 +1438,7 @@
</url>
<url>
<loc>https://www.ioccc.org/1990/baruch/index.html</loc>
<lastmod>2025-01-10T06:51:37+00:00</lastmod>
<lastmod>2025-04-29T18:15:00+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/1990/baruch/Makefile</loc>
@@ -1446,7 +1446,7 @@
</url>
<url>
<loc>https://www.ioccc.org/1990/baruch/README.md</loc>
<lastmod>2025-01-10T06:43:52+00:00</lastmod>
<lastmod>2025-04-29T18:11:24+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/1990/baruch/try.sh</loc>
@@ -15414,11 +15414,11 @@
</url>
<url>
<loc>https://www.ioccc.org/bugs.html</loc>
<lastmod>2025-04-16T17:16:09+00:00</lastmod>
<lastmod>2025-04-29T18:05:32+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/bugs.md</loc>
<lastmod>2025-04-16T17:15:59+00:00</lastmod>
<lastmod>2025-04-29T18:09:36+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/CODE_OF_CONDUCT.html</loc>
@@ -15482,7 +15482,7 @@
</url>
<url>
<loc>https://www.ioccc.org/location.html</loc>
<lastmod>2025-04-16T17:10:51+00:00</lastmod>
<lastmod>2025-04-29T18:13:49+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/Makefile</loc>
@@ -15598,7 +15598,7 @@
</url>
<url>
<loc>https://www.ioccc.org/status.html</loc>
<lastmod>2025-04-28T20:35:39+00:00</lastmod>
<lastmod>2025-04-29T18:20:29+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/status.json</loc>