John the Ripper

Out of all of our synthetic benchmarks, John the Ripper is perhaps the most robust; we can benchmark a wide range of encryption algorithms with many or no options very easily and quickly. For this benchmark, we downloaded John the Ripper 1.6. We had originally intended to build the program with the generic Linux make configuration. Unfortunately, John did not want to play nicely with that idea. We only ran the Intel CPU with HyperThreading for this portion of the benchmark.

linux:~/john-1.6/src # make linux-x86-any-elf
ln -sf x86-any.h arch.h
make ../run/john ../run/unshadow ../run/unafs ../run/unique \
JOHN_OBJS="DES_fmt.o DES_std.o BSDI_fmt.o MD5_fmt.o MD5_std.o BF_fmt.o BF_std.o AFS_fmt.o LM_fmt.o batch.o bench.o charset.o common.o compiler.o config.o cracker.o external.o formats.o getopt.o idle.o inc.o john.o list.o loader.o logger.o math.o memory.o misc.o options.o params.o path.o recovery.o rpp.o rules.o signals.o single.o status.o tty.o wordlist.o unshadow.o unafs.o unique.o x86.o" \
CFLAGS="-c -Wall -O2 -fomit-frame-pointer -m486"
make[1]: Entering directory '/root/john-1.6/src'
gcc -c -Wall -O2 -fomit-frame-pointer -m486 -funroll-loops DES_fmt.c
'-m486' is deprecated. Use '-march=i486' or '-mcpu=i486' instead.
cc1: error: CPU you selected does not support x86-64 instruction set
make[1]: *** [DES_fmt.o] Error 1
make[1]: Leaving directory '/root/john-1.6/src'
make: *** [linux-x86-any-elf] Error 2

Undeterred, we proceeded to build John with the generic configuration instead. John optimizes itself during the build, so you may view the builds of each configuration here (Intel) and here (AMD).

For those of you who downloaded the text files, you already know that the Intel CPU has pulled ahead, at least according to John. Below are some of the scores John posted while testing the utility.

John the Ripper 1.6 - Blowfish x32

John the Ripper 1.6 - FreeBSD MD5

John the Ripper 1.6 - DES x725 64/64 BS

As we saw in the intensive math benchmarks, the Athlon 64 has trouble keeping up with the Intel CPU.

Synthetic Benchmarks (continued) Conclusions
Comments Locked

275 Comments

View All Comments

  • Jeff7181 - Monday, August 9, 2004 - link

    Ooops... I really wish it was possible to edit these. =) What I meant to say was...

    "... especially since 2/3 of those benchmarks..."
  • Jeff7181 - Monday, August 9, 2004 - link

    I would like to see some Pentium 4 3.6 GHz numbers in there too so we can see the effect of Intel's x86-64 support. With the data available, it's impossible to decide whether Intel has integrated it properly and gets a performance boost, or if a 3.6 GHz Xeon is just naturally that much faster than an Athlon-64 3500+... especially since 92/3 of those benchmarks are not benchmarks I've ever seen you run before so I have no idea how ANY other processor compares.

    Sorry Kristopher, but this was a BAD article. There's not nearly enough information to draw any useful conclusions.
  • gimp0 - Monday, August 9, 2004 - link

    this was probably the worst comparison ever. At least give us some game benchmarks like UT2004 64bit and let us see some real numbers.

    Server CPU against a mianstream chip in a database environment will surely favor the xeon.

    whatever though
  • the5thgeek - Monday, August 9, 2004 - link

    what is the reason for comparing the new intel processor against the slowest socket 939 processor? why not a FX53 or 3800?
  • DrMrLordX - Monday, August 9, 2004 - link

    What the hell made you run a 3.6 ghz Nocona vs the 3500+?!? Try running it against an Opteron 150! For crying out loud . . .

Log in

Don't have an account? Sign up now