Download raw body.
Workflow question, maybe bug or unclear usage.
On 2022-01-28 1:59 p.m., Stefan Sperling wrote:
> On Fri, Jan 28, 2022 at 09:39:18PM +0100, Christian Weisgerber wrote:
>> Stefan Sperling:
>>
>>> This does not account for the full difference you see on NFS, so there
>>> could be ways to improve performance. Our DT_UNKNOWN workaround causes
>>> additional stat calls, so perhaps adding the -l mount option will help
>>> a bit?
>>
>> I tried that yesterday, but it didn't make any difference.  "got status"
>> of OpenBSD /usr/src on an NFS filesystem took 3 min 20 s on an APU2,
>> with and without -l.
> 
> Do you happen to know how this compares to CVS?
On NFS with older sparc64 system:
This give verbose and rather unusable output sadly
$ cvs status
<giant snip>
8m28.11s real     0m50.30s user     1m34.73s system
the more usable update with no changes command is slightly faster
$ cvs -Q -n update
    7m43.29s real     0m30.20s user     1m29.89s system
though I notice that it's not suppressing the cvs server: New directory
as I expected it too but that's a bug with a different versioning
software .... :P
In summary cvs is about 3-4 minutes faster for equivalent operation on
the entire openbsd tree on an older sparc64 processor (on nfs) than got
in it's current incarnation.
-- 
Ted Bullock <tbullock@comlore.com>
Workflow question, maybe bug or unclear usage.