[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <537A7EF2.60409@bitmessage.ch>
Date: Mon, 19 May 2014 22:00:18 +0000
From: yungai <BM-2DBq3nJF7GXKr6Nk6EHzvxxGBec6gQn2NB@...message.ch>
To: john-users@...ts.openwall.com
Subject: Re: memory issues: john is eating it all (descrypt-opencl)
> Yes, descrypt-opencl appears to be leaking memory. In the recent
> contest, I was running "--format=descrypt-opencl --fork=4" on a 7970
> (the --fork=4 results in much greater performance at this format, since
> otherwise the GPU would stay mostly idle waiting for data from host).
> This consumed about 6 GB of RAM (about 1.5 GB per forked process) in
> about 10 hours. I was going to report it to Sayantan on john-dev, but
> you were quicker to bring the same issue up.
Thank you for your fast reply.
I'm running a similar setup (--fork=2 on a 7990).
After reading your post I'm wondering if I should run --fork=8 instead? :)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
