https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253968

--- Comment #5 from Mark Millard <marklmi26-f...@yahoo.com> ---
(In reply to rkoberman from comment #4)

Doing "make fetch" and "make extract" for www/firefox is
something I can try on a 128 GiBYTe RAM ThreadRipper 1950X
that uses 960 GiByte Optane media and is running main
(14-CURRENT) from back on 2021-Feb-08. (Optane does not use
trim and is fast.) UFS2+SU (no J). The example context
predates any recent potential fixes. So . . .

Doing similar "time -l" might happen to expose something
common to the good vs. bad cases for those were the issue
stands out in their context.

# time -l make extract
===> Options unchanged
===>   firefox-85.0.2,2 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by firefox-85.0.2,2 for building
===>  Extracting for firefox-85.0.2,2
=> SHA256 Checksum OK for firefox-85.0.2.source.tar.xz.
       70.10 real        23.54 user        18.01 sys
     77540  maximum resident set size
        50  average shared memory size
        10  average unshared data size
       130  average unshared stack size
     37678  page reclaims
         0  page faults
         0  swaps
     12848  block input operations
   1175850  block output operations
        83  messages sent
        79  messages received
         0  signals received
   1188850  voluntary context switches
      1816  involuntary context switches

# time -l rm -fr /wrkdirs/usr/ports/www
       17.36 real         0.24 user         6.51 sys
      4116  maximum resident set size
         8  average shared memory size
         4  average unshared data size
       134  average unshared stack size
       587  page reclaims
         0  page faults
         0  swaps
         2  block input operations
    555695  block output operations
         0  messages sent
         0  messages received
         0  signals received
    607758  voluntary context switches
         0  involuntary context switches

(No other www/ content.) Looks like "block
output operations" and "voluntary context
switches" are what has lots of examples in
this context.


For reference: main 3acea07c1873 based:

# ~/fbsd-based-on-what-freebsd-main.sh 
merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b
merge-base: CommitDate: 2021-02-08 19:15:21 +0000
c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in git
context.
3acea07c1873 (pure-src) Restore the augmented strlen commentary
FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n244686-c1845d00f818
GENERIC-NODBG  amd64 amd64 1400004 1400004


I may be able to do similarly on some aarch64 SSD
based machines (that would have trim involved).

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to