|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc |
|
| #
8cdef6cb |
| 06-Dec-2016 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Increase worst-case maximum exec rate
* The pid reuse algorithm limits the maximum fork rate. This limit
was set too low. Increase the limit from 10000/sec to 100000/sec.
Currently ou
kernel - Increase worst-case maximum exec rate
* The pid reuse algorithm limits the maximum fork rate. This limit
was set too low. Increase the limit from 10000/sec to 100000/sec.
Currently our opteron maxes out at 43000/sec.
Note that with 999999 pids and a 10-second mandatory reuse time
floor there isn't much of a point increasing the limit beyond
100000/sec.
100,000/sec. Currently our opteron maxes out at around
43,000/sec (vfork/exec/wait3/exit of a small static binary).
* The domain reuse array was increased to 1MB to accomodate this
change. In addition, update the array in a cache-friendly manner.
* Modify test/sysperf/exec1 to take a nprocesses argument for the
timing run.
show more ...
|
|
Revision tags: v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
| #
43b3c06f |
| 14-Apr-2004 |
Matthew Dillon <dillon@dragonflybsd.org> |
Run the exec test for 5 seconds instead of 1 to improve measurement
statistics.
|
| #
6157d9fc |
| 10-Apr-2004 |
Matthew Dillon <dillon@dragonflybsd.org> |
Add vfork/exec perf test. exec1 tests static binaries, exec2 tests dynamic
binaries (you can test resident dynamic binaries by 'resident /tmp/exec2'
and then running /tmp/exec2).
|