Subject: Discussion related to cado-nfs
List archive
Re: [Cado-nfs-discuss] [Enquiry] What is the maximum DLP-bit prime size that CADO-NFS-DLP can solve? (For 1-4 processors)
Chronological Thread
- From: Pierrick Gaudry <pierrick.gaudry@loria.fr>
- To: Tay Boon Siang <tboonsia@dso.org.sg>
- Cc: "cado-nfs-discuss@lists.gforge.inria.fr" <cado-nfs-discuss@lists.gforge.inria.fr>
- Subject: Re: [Cado-nfs-discuss] [Enquiry] What is the maximum DLP-bit prime size that CADO-NFS-DLP can solve? (For 1-4 processors)
- Date: Thu, 20 Jul 2017 07:44:00 +0200
- List-archive: <http://lists.gforge.inria.fr/pipermail/cado-nfs-discuss/>
- List-id: A discussion list for Cado-NFS <cado-nfs-discuss.lists.gforge.inria.fr>
Hi,
Currently CADO-NFS for DLP is distributed with parameters for only the
following sizes: 60 digits, 100 digits, 155 digits, and no effort was
made to optimize them. The first two sizes are feasible with only a few
cores. For 155, that would mean months or possibly years of computation in
your setting.
Note that there are also parameters for DLP for 30 digits that we use for
testing; that one takes minutes or less.
Regards,
Pierrick
On Thu, Jul 20, 2017 at 12:41:10AM +0000, Tay Boon Siang wrote:
> Dear Sir/Mdm,
>
> I am currently doing a project on DLP and would like to use CADO-NFS in my
> project. However, due to lack of prior experience, I would just like to ask
> what is the maximum DLP-bit prime size that CADO-NFS-DLP can solve? (For
> 1-4 processors) to get an idea of the time I am looking at.
>
> Thank you.
> _______________________________________________
> Cado-nfs-discuss mailing list
> Cado-nfs-discuss@lists.gforge.inria.fr
> https://lists.gforge.inria.fr/mailman/listinfo/cado-nfs-discuss
- [Cado-nfs-discuss] [Enquiry] What is the maximum DLP-bit prime size that CADO-NFS-DLP can solve? (For 1-4 processors), Tay Boon Siang, 07/20/2017
- Re: [Cado-nfs-discuss] [Enquiry] What is the maximum DLP-bit prime size that CADO-NFS-DLP can solve? (For 1-4 processors), Pierrick Gaudry, 07/20/2017
Archive powered by MHonArc 2.6.19+.