You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
using all threads is nice for me, but its bad on a shared machine
$ nproc
128
$ rar2john asdf.rar > asdf.rar.hashes
$ john asdf.rar.hashes
Will run 128 OpenMP threads
$ john --node=1-1/4 asdf.rar.hashes
Will run 128 OpenMP threads
$ john --fork=1 asdf.rar.hashes
--fork number must be between 2 and 1024
$ john --fork=2 asdf.rar.hashes
Will run 64 OpenMP threads per process (128 total across 2 processes)
$ cpulimit --help
Usage: cpulimit [OPTIONS...] TARGET
OPTIONS
-l, --limit=N percentage of cpu allowed from 0 to 12800 (required)
-v, --verbose show control statistics
-z, --lazy exit if there is no target process, or if it dies
-i, --include-children limit also the children processes
-h, --help display this help and exit
TARGET must be exactly one of these:
-p, --pid=N pid of the process (implies -z)
-e, --exe=FILE name of the executable program file or path name
COMMAND [ARGS] run this command and limit it (implies -z)
$ cpulimit --limit=3200 --include-children john asdf.rar.hashes
Will run 128 OpenMP threads
this still uses all threads, but limits the cpu load to 25% per thread
The text was updated successfully, but these errors were encountered:
currently, i cannot limit the number of threads
using all threads is nice for me, but its bad on a shared machine
john version 9f913a7
john --list=build-info
workaround
this still uses all threads, but limits the cpu load to 25% per thread
The text was updated successfully, but these errors were encountered: