Open source?

log in

Advanced search

Message boards : Questions/Problems/Bugs : Open source?

Author Message
Profile den777
Send message
Joined: 13 Jan 14
Posts: 1
Credit: 543,292
RAC: 0
Message 1751 - Posted: 9 Mar 2017, 12:32:31 UTC

Are the applications used in this project open source software?

Robert Silverman
Send message
Joined: 23 May 16
Posts: 11
Credit: 0
RAC: 0
Message 1752 - Posted: 9 Mar 2017, 13:55:40 UTC - in response to Message 1751.

Yes

Bryan
Send message
Joined: 20 Mar 17
Posts: 4
Credit: 841,164
RAC: 154
Message 1754 - Posted: 20 Mar 2017, 4:44:44 UTC - in response to Message 1752.

Where is the source? (My search foo has so far failed)

Any optimizations that could be done? (in general or for specific architectures)

Robert Silverman
Send message
Joined: 23 May 16
Posts: 11
Credit: 0
RAC: 0
Message 1755 - Posted: 20 Mar 2017, 12:58:43 UTC - in response to Message 1754.

The source is msieve and GGNFS. see, e.g. sourceforge

When you ask about optimizations, I assume you mean
ADDITIONAL optimizations, besides those that have
already been done?

This code is heavily optimized already. Any additional
optimizations, absent new mathematical ideas, will provide
marginal improvement at best.

Bryan
Send message
Joined: 20 Mar 17
Posts: 4
Credit: 841,164
RAC: 154
Message 1756 - Posted: 22 Mar 2017, 2:55:40 UTC - in response to Message 1755.

Thanks for info where the source lives...

Seems Msieve at least has had some improvements since NFS@Home could have pulled it - at least for Linux: https://sourceforge.net/p/msieve/news/?source=navbar

The biggest change seems to be in 1.5.2 release with big improvements in CPUs. That could be in the 16e version for Windows (30 Jul 2014), but not in the Linux version (6 May 2012).

*App versions -https://escatter11.fullerton.edu/nfs/apps.php

jasonp
Send message
Joined: 5 Nov 13
Posts: 10
Credit: 368,336
RAC: 0
Message 1758 - Posted: 1 Apr 2017, 19:02:57 UTC

There are two codebases involved here: we use the sieving tools from GGNFS and the Msieve code for finishing off each factorization. Neither have had serious updates in a while. The GGNFS sieving tools are very good at their job and contain a ton of assembly language for various CPUs, but they are also very difficult to understand and modify with confidence. Msieve is not an application that the BOINC project distributes, finishing each factorization does not run very well in parallel and is not amenable to using BOINC resources. I am the Msieve maintainer and welcome some help, but I've been at this a long time and making the postprocessing faster is not easy.

So if you don't mind a steep learning curve, optimizing the sieving tools is the way to go. The 16e sieving source is here, though the BOINC modifications are not included (but easy).

jasonp
Send message
Joined: 5 Nov 13
Posts: 10
Credit: 368,336
RAC: 0
Message 1759 - Posted: 2 Apr 2017, 2:14:33 UTC

I should clarify: The 14e and 15e sieve applications use the lasieve4 source in the link I posted previously. The 16e sieve is a completely separate codebase with a link posted here. This is the code that the BOINC client distributes.

For Msieve, anyone who volunteers to run postprocessing is responsible for their own copy of the Msieve application. In practice version 1.52 has been available for a long time, and v1.53 was released a few months ago. I would expect most postprocessing volunteers run the latest and greatest.

Bryan
Send message
Joined: 20 Mar 17
Posts: 4
Credit: 841,164
RAC: 154
Message 1778 - Posted: 20 May 2017, 18:13:44 UTC - in response to Message 1759.

Thanks for explaining!

I've got a new AMD Ryzen CPU and was wondering if there was any optimizations that could be done to make it run faster/more efficiently on that arch. I'm happy to test if useful.

Message boards : Questions/Problems/Bugs : Open source?


Home | My Account | Message Boards