* Uploading of benchmark result data to OpenBenchmarking.org is always optional (opt-in) via the Phoronix Test Suite for users wishing to share their results publicly. ** Data based on those opting to upload their test results to OpenBenchmarking.org and users enabling the opt-in anonymous statistics reporting while running benchmarks from an Internet-connected platform. *** Test profile page view reporting began March 2021. Data updated weekly as of 14 May 2024.
Revision History
pts/john-the-ripper-1.8.0 [View Source] Fri, 17 Mar 2023 13:47:27 GMT Update against John The Ripper Git due to no official releases in several years... Build fixes.
pts/john-the-ripper-1.7.2 [View Source] Mon, 10 Feb 2020 11:53:21 GMT pts-core now handles K to numeric conversion so drop this faulty result-definition handling for certain cases of dynamic K.
pts/john-the-ripper-1.7.1 [View Source] Sat, 08 Feb 2020 10:14:09 GMT Fix for MD5 test run (JtR appending K to result, update parser) and Cygwin fix for Windows.
pts/john-the-ripper-1.7.0 [View Source] Fri, 21 Jun 2019 19:56:15 GMT Update against upstream JtR 1.9.0-jumbo-1.
pts/john-the-ripper-1.6.2 [View Source] Sat, 07 Apr 2018 20:53:08 GMT Use gmake on BSDs
pts/john-the-ripper-1.6.1 [View Source] Sat, 24 Mar 2018 18:01:13 GMT Disable the configure native-tests to avoid some odd AVX-related build errors being reported on Linux systems
pts/john-the-ripper-1.6.0 [View Source] Wed, 28 Feb 2018 11:30:09 GMT Update against JTR 1.8.0-jumbo-1, prep initial Windows support.
pts/john-the-ripper-1.5.1 [View Source] Sun, 10 Aug 2014 12:14:29 GMT Support for building John The Ripper on non-x86 architectures. Change submitted by Michael Schloh.
pts/john-the-ripper-1.5.0 [View Source] Fri, 10 Jan 2014 14:09:42 GMT Update against upstream John The Ripper 1.8.0.
pts/john-the-ripper-1.4.1 [View Source] Wed, 23 Jan 2013 13:14:38 GMT Disable the cache share since the latest JTR upstream version seems to have issues with the parsing when using the PTS cache share.
pts/john-the-ripper-1.4.0 [View Source] Thu, 04 Oct 2012 00:11:49 GMT Update against John The Ripper 1.7.9-jumbo-7 upstream plus use openssl-development external dependency.
pts/john-the-ripper-1.3.0 [View Source] Tue, 21 Feb 2012 10:45:27 GMT Set the OMPFLAGS on make.
pts/john-the-ripper-1.2.0 [View Source] Wed, 07 Dec 2011 12:26:09 GMT Update against John The Ripper 1.7.9 upstream.
pts/john-the-ripper-1.1.0 [View Source] Sat, 27 Aug 2011 14:09:59 GMT Update against upstream John 1.7.8.
pts/john-the-ripper-1.0.1 [View Source] Mon, 06 Dec 2010 14:53:59 GMT Initial import into OpenBenchmarking.org
OpenBenchmarking.org metrics for this test profile configuration based on 2,539 public results since 10 January 2014 with the latest data as of 4 December 2023.
Below is an overview of the generalized performance for components where there is sufficient statistically significant data based upon user-uploaded results. It is important to keep in mind particularly in the Linux/open-source space there can be vastly different OS configurations, with this overview intended to offer just general guidance as to the performance expectations.
Based on OpenBenchmarking.org data, the selected test / test configuration (John The Ripper 1.8.0 - Test: Traditional DES) has an average run-time of 4 minutes. By default this test profile is set to run at least 3 times but may increase if the standard deviation exceeds pre-defined defaults or other calculations deem additional runs necessary for greater statistical accuracy of the result.
Based on public OpenBenchmarking.org results, the selected test / test configuration has an average standard deviation of 1.8%.
Does It Scale Well With Increasing Cores?
No, based on the automated analysis of the collected public benchmark data, this test / test settings does not generally scale well with increasing CPU core counts. Data based on publicly available results for this test / test settings, separated by vendor, result divided by the reference CPU clock speed, grouped by matching physical CPU core count, and normalized against the smallest core count tested from each vendor for each CPU having a sufficient number of test samples and statistically significant data.
Notable Instruction Set Usage
Notable instruction set extensions supported by this test, based on an automatic analysis by the Phoronix Test Suite / OpenBenchmarking.org analytics engine.
The test / benchmark does honor compiler flag changes.
Last automated analysis: 18 March 2023
This test profile binary relies on the shared libraries libcrypto.so.3, libgmp.so.10, libm.so.6, libz.so.1, libcrypt.so.1, libbz2.so.1.0, libgomp.so.1, libc.so.6.
Tested CPU Architectures
This benchmark has been successfully tested on the below mentioned architectures. The CPU architectures listed is where successful OpenBenchmarking.org result uploads occurred, namely for helping to determine if a given test is compatible with various alternative CPU architectures.
Compare