mersenneforum.org  

Go Back   mersenneforum.org > Prime Search Projects > Prime Sierpinski Project

Reply
 
Thread Tools
Old 2008-04-15, 23:06   #45
VJS
 
VJS's Avatar
 
Dec 2004

13·23 Posts
Default

Your numbers look about right.

As we decrease the number of k's we decrease the efficiency of the sieve but that's what it is all about. Less k's less factors... less k's more speed...

Considering this k wasn't that heavy and the number we have sieve is obviously still good to go.

BTW, thanks for checking and posting the speed increase.
VJS is offline   Reply With Quote
Old 2008-05-01, 08:13   #46
hhh
 
hhh's Avatar
 
Jun 2005

22×3×31 Posts
Default

BTW, how deep can we sieve with sr2sieve? I can put hilarious lines in the sr2work.txt, like
999999999-1000000000
and it still starts crunching (That's about 1000 times deeper than what I am crunching right now); but are the results still reliable up there?

H.
hhh is offline   Reply With Quote
Old 2008-05-02, 01:45   #47
geoff
 
geoff's Avatar
 
Mar 2003
New Zealand

13×89 Posts
Default

Quote:
Originally Posted by hhh View Post
BTW, how deep can we sieve with sr2sieve? I can put hilarious lines in the sr2work.txt, like
999999999-1000000000
and it still starts crunching (That's about 1000 times deeper than what I am crunching right now); but are the results still reliable up there?

H.
It should produce correct results for factors up to 2^62, or about 4.6e18.

It will not necessarily run efficiently at that depth though. There will be some slowdown of the modular multiplication routines between 2^61 and 2^62 due to branch mispredictions. Also I haven't tested the performance of the prime sieve at that depth (it might spend to much time sieving for prime candidate factors when it would be faster just to let some composite ones through).

Last fiddled with by geoff on 2008-05-02 at 01:50
geoff is offline   Reply With Quote
Old 2008-05-02, 11:12   #48
Lennart
 
Lennart's Avatar
 
"Lennart"
Jun 2007

46016 Posts
Smile

Quote:
Originally Posted by dspdude2000 View Post
Oh, you're right. That seems needlessly confusing. I guess I'd have to run sr2sieve manually to make a comparison. Maybe I'll do that.

Here you have the WU info on PG.
sr2sieve -p3710472300e6 -P3710473075e6

/Lennart
Lennart is offline   Reply With Quote
Old 2008-07-12, 11:43   #49
hhh
 
hhh's Avatar
 
Jun 2005

22·3·31 Posts
Default

Am I mistaken or should there be a speed advantage for 64bit?

I installed Ubuntu on a USB stick using the 64bit CD, and get 660 kp/s, instead of up to 700kp/s in Windows XP32, what am I doing wrong?

H.
hhh is offline   Reply With Quote
Old 2008-07-12, 16:21   #50
benjackson
 
Aug 2007
Princeton, NJ

2·5 Posts
Default

Quote:
Originally Posted by hhh View Post
Am I mistaken or should there be a speed advantage for 64bit?

I installed Ubuntu on a USB stick using the 64bit CD, and get 660 kp/s, instead of up to 700kp/s in Windows XP32, what am I doing wrong?

H.
Go to a console and type uname -m and make sure it's x86_64 to check that you're using 64bit linux. Otherwise, make sure that you're using the 64bit sr2sieve as well. You can do that by using readelf -a sr2sieve | grep Machine: and seeing if it says X86-64. What type of processor are you using? What version of Ubuntu, I'm assuming 8.04. There shouldn't be any other libraries you need installed so I'm not sure what to tell you. What type/speed processor do you have? Any C2D should be getting well above 660 per core in 64bit mode.
benjackson is offline   Reply With Quote
Old 2008-07-12, 19:07   #51
hhh
 
hhh's Avatar
 
Jun 2005

22×3×31 Posts
Default

ja, ja, Hardy Heron, x86_64, Machine: Advanced Micro Devices X86-64. C2D T5600.

As I said, on pendrive, but persistent install. Installationwise, you can talk about a pain in the bottom. So many HowTo's out there, none works: you have to search your information at 5 different places and be imaginative. And of course, the keyboard layout is the only thing that isn't saved.

I'm a bit frustrated. I mean it's cool, and works, finally, but it's not what I imagined. But hey, right?

Back to my problem. I have not the slightest idea, but could it be that the processor is sleeping all the time at 1 GHz instead of 1.83, and that multiplied with the better performance, it gives me about the same thing as full throttle 32bit?

H.
hhh is offline   Reply With Quote
Old 2008-07-14, 03:35   #52
geoff
 
geoff's Avatar
 
Mar 2003
New Zealand

13×89 Posts
Default

Quote:
Originally Posted by hhh View Post
Back to my problem. I have not the slightest idea, but could it be that the processor is sleeping all the time at 1 GHz instead of 1.83, and that multiplied with the better performance, it gives me about the same thing as full throttle 32bit?
Try running sr2sieve with the -Z switch to prevent it lowering priority to idle. Newer Linux distributions run the CPU at low frequency if all running processes are at idle priority. You can disable this in the system configuration somewhere, or in the BIOS menus if that doesn't work.

I have thought about changing the default priority for sr2sieve, but I am not quite sure what the best default should be.

the 64-bit version should run at least 1.5x faster than the 32-bit version on Core 2 CPUs, closer to 2x faster when the n-range is very large as with PSP/SOB.
geoff is offline   Reply With Quote
Old 2008-07-14, 04:23   #53
geoff
 
geoff's Avatar
 
Mar 2003
New Zealand

13·89 Posts
Default

If you need a sanity check on the sieve speed, the last range I did was 12323060-12324060 which ran at about 1750 kp/s on a 2.66 GHz Core 2 Duo in 64-bit mode, or at about 3400 kp/s using two cores with the -t2 switch.
geoff is offline   Reply With Quote
Old 2008-07-14, 10:20   #54
hhh
 
hhh's Avatar
 
Jun 2005

22×3×31 Posts
Default

Thanks Lennart and geoff, the -Z swich did the trick. Now I'm getting 2Mp/s, instead of 1.3Mp/s.

But this pendrive install still doesn't convince me. Booting takes forever, for instance. One day, I will have to put a real one on the HD.

H.
hhh is offline   Reply With Quote
Old 2008-07-15, 16:50   #55
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

141418 Posts
Default

Quote:
Originally Posted by geoff View Post
Try running sr2sieve with the -Z switch to prevent it lowering priority to idle. Newer Linux distributions run the CPU at low frequency if all running processes are at idle priority. You can disable this in the system configuration somewhere, or in the BIOS menus if that doesn't work.

I have thought about changing the default priority for sr2sieve, but I am not quite sure what the best default should be.

the 64-bit version should run at least 1.5x faster than the 32-bit version on Core 2 CPUs, closer to 2x faster when the n-range is very large as with PSP/SOB.
Yeah, I've run into this same problem on Ubuntu 8.04 32-bit. My solution is to put one CPU Frequency Scaling Monitor on my taskbar for each core, and then use it to manually put the CPU into performance mode (i.e. no clocking down whatsoever) at each bootup. Through some research online I've traced this down to a flag in a certain file that's causing the problem--yes, you can fix it, but it will be back to "normal" at the next reboot. When I get around to it I'll report it on the Ubuntu message boards, hopefully they'll get it fixed in the next version (8.10).
mdettweiler is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
srsieve/sr2sieve enhancements rogue Software 281 2020-09-29 16:36
32-bit of sr1sieve and sr2sieve for Win pepi37 Software 5 2013-08-09 22:31
sr2sieve question SaneMur Information & Answers 2 2011-08-21 22:04
How to use sr2sieve nuggetprime Riesel Prime Search 40 2007-12-03 06:01
Sr2sieve on PPC/Linux BlisteringSheep Sierpinski/Riesel Base 5 172 2007-07-06 21:29

All times are UTC. The time now is 14:58.

Thu Oct 22 14:58:03 UTC 2020 up 42 days, 12:09, 1 user, load averages: 1.88, 1.87, 1.84

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.