Follow-up Comment #8, bug #68145 (group groff): [comment #7 comment #7:] > I still can't reproduce this.
This is strange.
Slightly different measurement method: measured execution time of grotty
processing ditroffs generated using different versions of macro-directories.
#!/bin/bash -e
for ((n=1; n<=64; n*=2)); do
for v in 23 24; do
for ((i=1; i<=$n; i++)); do
cat bash.1
done | troff -M groff-1.$v.0/tmac/ -man -Tutf8 >
bash_troff-1.$v.0.ditroff
done
for v in 23 24; do
declare "dur$v"=$(/usr/bin/time -f "%U" grotty <
bash_troff-1.$v.0.ditroff 2>&1 > /dev/null)
done
printf "% 3s\t% 4s\t% 4s\n" $n $dur23 $dur24
done
gives
1 0.12 0.12
2 0.23 0.28
4 0.47 0.62
8 0.94 1.59
16 1.87 4.56
32 3.75 14.31
64 7.49 63.89
Maybe measurement method is wrong, or some quirks of my system. However,
increase of man pages rendering time noticed not only by me.
Do I understand correctly that -M option overrides default search paths, not
appends specified one to default?
Should I attach ditroffs generated in both cases on my side?
Just noticed that output from grotty processing 1.23.0 ditroff appears in
terminal immediately while processing. But grotty processing 1.24.0 is quiet,
and output appears only at the very end.
Valgrind also shows difference in allocated memory (single bash.1 copy used as
input):
$ valgrind grotty < ./bash_troff-1.23.0.ditroff > /dev/null
...
==11110== HEAP SUMMARY:
==11110== in use at exit: 24,957 bytes in 1,754 blocks
==11110== total heap usage: 619,653 allocs, 617,899 frees, 97,048,485 bytes
allocated
$ valgrind grotty < ./bash_troff-1.24.0.ditroff > /dev/null
...
==11151== HEAP SUMMARY:
==11151== in use at exit: 24,957 bytes in 1,754 blocks
==11151== total heap usage: 618,293 allocs, 616,539 frees, 195,303,380 bytes
allocated
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68145>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
