From c014fbffff8e35f773c5c797ddeaae59367176a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?John=20Ankarstr=C3=B6m?= Date: Wed, 11 Nov 2020 11:02:36 +0100 Subject: add performance info to manual --- rf | 1 - rf.1 | 16 +++++++++++++++- 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/rf b/rf index ec47269..f99a239 100755 --- a/rf +++ b/rf @@ -97,7 +97,6 @@ for (@lines) { # Reference definition if (/^\.R! (\d+)/) { print fmt($format_list, $1, 1) . "\n"; - next; } diff --git a/rf.1 b/rf.1 index ad9d2bd..d6d16ca 100644 --- a/rf.1 +++ b/rf.1 @@ -20,7 +20,7 @@ in a couple important ways: .Bl -enum .It References are not stored in a separate file. -They are defined via macros in the troff document itself. +They are defined via macros in the troff document itself, usually at the end. .Pp This means that you can move, copy and share your troff document without needing to worry about an additional reference file. Furthermore, you never run the risk of accidentally losing the references attached to a document. @@ -37,6 +37,20 @@ is much more simple and offers much more basic functionality than .Xr refer 1 . This means that you can learn all of it in five minutes. .El +.Pp +The performance of +.Nm +primarily depends on the number of entries in the reference list at the end of the document. +On my HP Compaq dc5700 from 2007, the relationship between number of entries in the reference list and total execution time is roughly the following: +.Bl -column "Entries " "Time " -offset indent +.It Em Entries Ta Em Time +.It 3 Ta 0.03s +.It 50 Ta 0.09s +.It 107 Ta 0.15s +.It 182 Ta 0.24s +.El +.Pp +I would deem it rare to have more than a couple of hundred references in a troff document. . .Sh USAGE .Nm -- cgit v1.2.3