How long is too long?

ThomRuley · 2013-11-26, 02:46

C110, older Pentium M processor (1.6GHz), no CUDA, running polynomial selection for about 24 hours so far.

Is something wrong? And how would I know?

LaurV · 2013-11-26, 03:31

Quote:

Originally Posted by ThomRuley

C110, older Pentium M processor (1.6GHz), no CUDA, running polynomial selection for about 24 hours so far.

Is something wrong? And how would I know?

Nothing wrong. You don't have a timeout

You can try to find a better and better poly, for years, if you like... (well... is not so efficient...)

For a comparison: Single core time for a C110 in the factor.log file of yafu (which uses msieve for poly selection) is set to about 3400 seconds (I used 1 core of a Core2Duo CPU to check just now). So, most probably, you have already a very good poly.

Advice: if msieve looks complicate for you, try using yafu for a while. It does the most of the things for you, it is much easier for a start.

jasonp · 2013-11-26, 19:00

The development version of Msieve has a fix for a bug that messes up the calculation of elapsed time in Windows; v1.51 unfortunately does not have the fix.

EdH · 2013-11-30, 04:52

If you are still using factmsieve.py, you can set:

...
USE_CUDA = False
GPU_NUM = 0
MSIEVE_POLY_TIME_LIMIT = 0
...

to a hard time in minutes. (0 means to use msieve's timing.) But, I would first look in the .log file to see how long msieve wants to search. It will say something like:

poly select deadline: 15264
time limit set to 4.24 CPU-hours

The 15264 is CPU-seconds

2013-11-26, 02:46	#1
ThomRuley May 2003 2·3·7² Posts	How long is too long? C110, older Pentium M processor (1.6GHz), no CUDA, running polynomial selection for about 24 hours so far. Is something wrong? And how would I know?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
very long int	davar55	Lounge	60	2013-07-30 20:26
How long until annihilation?	Zeta-Flux	Soap Box	26	2011-10-19 00:51
Using long long's in Mingw with 32-bit Windows XP	grandpascorpion	Programming	7	2009-10-04 12:13
I think it's gonna be a long, long time	panic	Hardware	9	2009-09-11 05:11
How long is too long?	schickel	Lounge	2	2009-02-22 12:31

2013-11-26, 19:00	#3
jasonp Tribal Bullet Oct 2004 110111101101₂ Posts	The development version of Msieve has a fix for a bug that messes up the calculation of elapsed time in Windows; v1.51 unfortunately does not have the fix.

2013-11-30, 04:52	#4
EdH "Ed Hall" Dec 2009 Adirondack Mtns 3·7·263 Posts	If you are still using factmsieve.py, you can set: ... USE_CUDA = False GPU_NUM = 0 MSIEVE_POLY_TIME_LIMIT = 0 ... to a hard time in minutes. (0 means to use msieve's timing.) But, I would first look in the .log file to see how long msieve wants to search. It will say something like: poly select deadline: 15264 time limit set to 4.24 CPU-hours The 15264 is CPU-seconds