pyrit 0.2.3 decrease k/s than BT4

[GoogleCodeExporter]

What steps will reproduce the problem?

1.
2.
3.

What is the expected output? What do you see instead?
similar or better k/s. Instead, performance decrease.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Hardware: CPU Phenom 2 4 core@2.8Ghz, NVIDIA 9800GTX+

Pyrit benchmark in BackTrak4 live (prefinal live) reports 1000 k/s on CPU 4
core (in that version there was not support for SSE2) and 7440k/s for GPU. 
(I dont know version of pyrit in BT4 but for sure is before v112)

2 days ago, I recompiled pyrit (following these instructions
http://code.google.com/p/pyrit/wiki/Installation) on ubuntu 9.04 at 64bit
(pyrit 0.2.3, CUDA driver 190.18, cudatoolkit 2.3) and pyrit benchmark is
about 640 k/s for each CPU core (3 core running, core #4 dedicated to serve
GPU) and the GPU report about 6900-7000 k/s.

Why now GPU loose about 450-500K/s if compared with old version of pyrit
present on BackTrack4? I tried to not start X server in ubuntu and test
pyrit from command line, but it never reach 7440 k/s. 

So, what is wrong?

- Maybe there are some flag to set during compilation to use GPU in
optimized way? 
- Maybe pyrit in BT4 runs better because it is at 32bits? 
- Maybe because BT4 is a more "light" OS than Ubuntu?

Original issue reported on code.google.com by pyrit.lo...@gmail.com on 6 Aug 2009 at 12:24

[GoogleCodeExporter]

You should try running Pyrit for at least several minutes. It takes some time 
for all
the buffering to come up with optimal values.

Original comment by lukas.l...@gmail.com on 8 Aug 2009 at 4:47

[GoogleCodeExporter]

hi likas, thanks for suggestion.
Im not at home, so i can not do immediately: till now i did only "pyrit 
benchmark" 
without use it on real situation.

Does it exist a option to set the how much long test must run? (i.e. pyrit 
benchmark 
--minutes=30) ?

Original comment by pyrit.lo...@gmail.com on 10 Aug 2009 at 10:49

[GoogleCodeExporter]

Won't be able to track that. Closed for good.

Original comment by lukas.l...@gmail.com on 4 Oct 2009 at 5:03

• Changed state: WontFix