so have u tried the same compilation on another pc

[QUOTE=R.D. Silverman;120449]Have you checked memory usage/paging while it is running?

It sounds WEIRD.[/QUOTE]Yup, checked all the obvious things. It's running on a machiene with 2G physical memory and the VM usages is well in line with Franke's siever running on a Linux box.

I agree, it is weird. If the speed difference was only a factor of 5 I'd shrug and mutter about 64-bit vs 32-bit or Cygwin vs Gentoo Linux, but a factor of 100 is so big that there must be something completly silly I'm overlooking.


Paul

[QUOTE=xilman;120483]Yup, checked all the obvious things. It's running on a machiene with 2G physical memory and the VM usages is well in line with Franke's siever running on a Linux box.

I agree, it is weird. If the speed difference was only a factor of 5 I'd shrug and mutter about 64-bit vs 32-bit or Cygwin vs Gentoo Linux, but a factor of 100 is so big that there must be something completly silly I'm overlooking.


Paul[/QUOTE]

Are you running the p4 executables in cygwin?

[QUOTE=smh;120489]Are you running the p4 executables in cygwin?[/QUOTE]Yes.

That might be the "ah-ha" moment...


Paul

[QUOTE=xilman;120491]Yes.

That might be the "ah-ha" moment...


Paul[/QUOTE]
I don't have cygwin installed, so can't test this for you.

[QUOTE=smh;120489]Are you running the p4 executables in cygwin?[/QUOTE]Made no discernible difference when runing under cmd.exe:sad:

Thanks, everyone, for all your help. I think I'll abandon this approach for the time being and see whether I can get a lattice siever built from source (either Franke's original or ggnfs) under Cygwin.

Paul

the def-nm-params.txt file i have got it only has params for =>98 digits which means testing numbers lower than that take ages because of poly selection being too high
does anyone one have parameters for <98 digits

thanks henryzz

If you have to cut down a large tree would you use a chain saw or table knife for the job?

If you have made yourself a nice steak for dinner, would you use use a chain saw or a table knife for the job?


Morale: Use an appropriate tool for the job at hand [HINT: Is the Number Field Sieve the best tool for the inputs you specify]?

--
Cheers,
Jes

i really want them for learning to use ggnfs but currently poly selection is taking similar time to running msieve for the whole factorization

[QUOTE=henryzz;121029]i really want them for learning to use ggnfs but currently poly selection is taking similar time to running msieve for the whole factorization[/QUOTE]
What you're seeing is the difference between the ordinary poly selection tools (which are incredibly fast) and the polyselect program in GGNFS. For small inputs you really need degree 4 polynomials, and only polyselect can generate those.

i am using factlat.pl which uses pol51m0b