search

jslhs / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

Pyrit batch shows false 0 PMK/s on non sse2 x86 cpus #258

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Pyrit 0.4.0 batch shows false 0 PMK/s  on non sse2 x86 cpus
2.
3.

What is the expected output? What do you see instead?

System is  clearly crunching and is making progress with work units, but
pyrit says 0 PMK/s

root@PowerEdge6300:/mnt/nfs# pyrit batch
Pyrit 0.4.0-dev (svn r288) (C) 2008-2010 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Connecting to storage at 'file://'...  connected.
Working on ESSID 'KTA3'
Processed 168/2048 workunits so far (8.2%); 0 PMKs per second.

What version of the product are you using? On what operating system?
Pyrit 0.4.0-dev (svn r288) 

Please provide any additional information below.

Non SSE2 cpus x86

Original issue reported on code.google.com by thefixe...@gmail.com on 4 Feb 2011 at 4:58

GoogleCodeExporter commented 8 years ago 
500 Mhz PowerEdge? Really? :-)

The problem is that Pyrit keeps track of the performance over a certain amount 
of time (in this case 60 seconds, irrc). If computation takes longer than 60 
seconds, the performance during that time will be Zero.

Original comment by lukas.l...@gmail.com on 4 Feb 2011 at 7:37

GoogleCodeExporter commented 8 years ago 
hehe yeah its a real piece of crap. i know its processing because its going 
through the work units and the db is growing

Original comment by thefixe...@gmail.com on 4 Feb 2011 at 10:28

GoogleCodeExporter commented 8 years ago 
BUT theres 4 of them, and I have many other shitboxes if we can get them 
running in tandem and add a couple pci Geforce 9500 cards will have cuda as 
well, main thing is im testing network functionality and thats the main issue 
we have atm.

Original comment by thefixe...@gmail.com on 4 Feb 2011 at 11:06

GoogleCodeExporter commented 8 years ago 
The PerformanceCounter-object should be more flexible

Original comment by lukas.l...@gmail.com on 11 Feb 2011 at 8:48

GoogleCodeExporter commented 8 years ago 
" Pyrit keeps track of the performance over a certain amount of time (in this 
case 60 seconds"

Um yeah shouldnt that be PMK per second? Not PMK per 60 seconds...

Just a thought

Original comment by mrfantas...@aol.com on 22 Feb 2011 at 1:42

GoogleCodeExporter commented 8 years ago 
Issue 270 has been merged into this issue.

Original comment by lukas.l...@gmail.com on 3 Mar 2011 at 7:49

GoogleCodeExporter commented 8 years ago 
Issue 273 has been merged into this issue.

Original comment by lukas.l...@gmail.com on 9 Mar 2011 at 7:31