Skip to Content.
Sympa Menu

cado-nfs - Re: [Cado-nfs-discuss] cado-nfs cmake build using icpc

Subject: Discussion related to cado-nfs

List archive

Re: [Cado-nfs-discuss] cado-nfs cmake build using icpc


Chronological Thread 
  • From: paul zimmermann <Paul.Zimmermann@inria.fr>
  • To: ƦOB COASTN <robertpancoast77@gmail.com>
  • Cc: cado-nfs-discuss@lists.gforge.inria.fr
  • Subject: Re: [Cado-nfs-discuss] cado-nfs cmake build using icpc
  • Date: Fri, 30 Oct 2015 10:45:15 +0100
  • 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,

> The baseline RSA120 results for the k1om benchmark are outlined below:
> dual 6core Intel(R) Xeon(R) CPU E52603 && (8) Xeon PHI 5110P
> RSA120: 1.65 hours = >1 day = 4.53089e+06/5940.38
>
> If we compare to the baseline for RSA120 on the cado homepage:
> dual 8core Intel(R) Xeon(R) CPU E52650
> RSA120: 43.9 hours = ~2 days = ~158040
>
> Comparison:
> It is unfair to directly compare 10 processors to 2, but here are the
> results anyway.
> 158040 / 5941 = 26.6x Speed-up!
> We could argue that they both exist as one computation node.

I'm not sure this comparison is correct. The 43.9 hours on
http://cado-nfs.gforge.inria.fr/ represent the total cpu time
of all 16 threads, thus the wall clock time was about 3 hours.
(Maybe we should also mention the wall clock time.)

I believe the 1.65 hours you mention represent the wall clock time,
not the total cpu time?

Paul




Archive powered by MHonArc 2.6.19+.

Top of Page