Closed GoogleCodeExporter closed 8 years ago
I speak in function of my experience and what I read on the issues in these
months, so it means I don't have the TRUE on my tongue, ok?
As far as I know, pyrit has problem to scale (see issue 173) and there are some
bottlenecks around (threads, moltiple GPU managements, etc) and there are also
other bottleneck (DB performace issues, Network I/O, hard disk I/O, etc).
If you want to follow the "cluster way", my suggestion is to set a few number
of nodes (lets start with one master and one slave) and then test. Then add a
new node and ther again till you reach bottleneck.
Anyway, I think you hard disk will be not able to feed 24 nodes: I think best
solution (under performances viewpoint) is manage 24 nodes indipendently,
charge 1/24th of passwords on each of them and then control from remote using
ssh and/or scripts.
In this case, you will have PSK/s that will grove in linear mode in function of
number of node, otherwise I am afraid you will suffer a lot of bottlenck than
will "eat" so many power.... c'est la vie!
PS: i don't think "issue" page is the best way to manage this topic, it should
be bettor to post in group discussion.
Original comment by pyrit.lo...@gmail.com
on 17 Jan 2011 at 12:20
would be nice to see unified clustering platform for worlds top cracking
programs
John the ripper has MPI support, if Pyrit has MPI support that would be nice
because it would allow both programs to run on the same distributed computing
platform
Original comment by thefixe...@gmail.com
on 1 Feb 2011 at 8:30
you are very welcome to write one :-)
Original comment by lukas.l...@gmail.com
on 2 Feb 2011 at 7:35
I have done the test with 20pc (19client + 1 server)
I will write the results as soon as possible
Original comment by andor...@gmail.com
on 2 Feb 2011 at 2:35
hey lucas, your awesome dude!! I wish I knew how to code I would help you but
im a n00b, I bow to thee, and thank you for making your work available.
Original comment by thefixe...@gmail.com
on 5 Feb 2011 at 5:05
Original comment by lukas.l...@gmail.com
on 15 Feb 2011 at 4:17
Original issue reported on code.google.com by
andor...@gmail.com
on 16 Jan 2011 at 11:54