| Author |
Message |
|---|
John Honorary cruncher
Send message
Joined: 21 Feb 06
Posts: 2875
ID: 2449
Credit: 2,681,934
RAC: 0
                 
|
|
Welcome to PrimeGrid's Birthday/Summer Solstice Challenge
PrimeGrid's Challenge series continues with the "Birthday/Summer Solstice Challenge". We are celebrating PrimeGrid's 6th birthday!!! Therefore, a 24 hour Challenge is being offered on PrimeGrid's Cullen/Woodall (Sieve) application. The celebration will culminate in the ancient observation of the Summer Solstice, 21 June!
This will mark PrimeGrid's 6th Birthday. Each year new projects are added, the tests become longer, and the problems become tougher to solve. Yet, this year has so far proven to be stellar for progress. This is a true testament to the dedicated crunchers who contribute their computing time to the project. Thank you to everyone who has joined the effort to find primes.
Usually at this time, we do our best to document the previous year's progress for historical purposes. However, to say the least, this endeavor has been difficult to maintain. Therefore, this year we hope to move this out of the forum and into PrimeGrid's Wiki. Please, if you have the interest and spare time, help update the History of PrimeGrid, Milestones, and Significant Primes.
For the old general background information in the forum, please visit PG History. For a list of accomplishments, please visit PG Milestones & Significant Primes. The move of this to the Wiki will hopefully allow it to be more up-to-date. [fingers crossed] :)
To participate in the Challenge, please select only the Cullen/Woodall (Sieve) project in your PrimeGrid preferences section. Also, set "Send work from any subproject if selected projects have no work" to no to guarantee that no other work will be sent. The Challenge will begin 20 June 2011 17:16 UTC and end 21 June 2011 17:16 UTC. Application builds are available for the following:
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.01
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.12 (cuda23)
- Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU 1.12
- Linux running on an Intel x86-compatible CPU 1.12
- Linux running on an Intel x86-compatible CPU 1.12 (cuda23)
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.12
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.12 (cuda23)
- Mac OS 10.3 or later running on Motorola PowerPC 1.12
- Mac OS 10.4 or later running on Intel 1.12
- Mac OS 10.4 or later running on Intel 1.12 (cuda32)
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.12
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.12 (cuda32)
Note: 64 bit CPU builds benefit from a 1.7X speed advantage over 32 bit CPU...so 1.7X the credit. :)
Recommendation: The Cullen/Woodall (Sieve) application requires a one time download of a 15MB sieve file. Please consider running a few Cullen/Woodall (Sieve) WU's before the Challenge begins so your client will already have the sieve file. This way, bandwidth can be used to deliver WU's instead of the sieve file. :) Thank you!
Time zone converter:
The servers are located in the Northern Hemisphere; therefore, we'll observe summer. However, the Southern Hemisphere will be experiencing the Winter Solstice.
The World Clock - Time Zone Converter
NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section to the left of the countdown clock.
Scoring Information
Scores will be kept for individuals and teams. Only work units issued AFTER 20 June 2011 17:16 UTC and received BEFORE 21 June 2011 17:16 UTC will be considered for credit. Since this is a fixed credit project, we'll be using cobblestones for scoring.
Credit is currently set at 364.43 cobblestones per WU.
About the Cullen/Woodall Prime Search
The Cullen/Woodall (Sieve) supports both the Cullen and Woodall Prime Searches.
About the Cullen Prime Search
Cullen Numbers are positive integers of the form Cn = n*2^n+1, where n is also a positive integer greater than zero. Cullen numbers that are prime are called Cullen primes.
The Cullen numbers Cn are primes for the following n:
1, 141, 4713, 5795, 6611, 18496, 32292, 32469, 59656, 90825, 262419, 361275, 481899, 1354828, 6328548, 6679881 and composite for all other n less than 8771732.
The Prime Pages keeps a list of the Top 20 Cullen Primes.
About the Woodall Prime Search
Woodall Numbers (sometimes called Cullen numbers 'of the second kind') are positive integers of the form Wn = n*2^n-1, where n is also a positive integer greater than zero. Woodall numbers that are prime are called Woodall primes (or Cullen primes of the second kind).
The Woodall numbers Wn are primes for the following n:
2, 3, 6, 30, 75, 81, 115, 123, 249, 362, 384, 462, 512, 751, 822, 5312, 7755, 9531, 12379, 15822, 18885, 22971, 23005, 98726, 143018, 151023, 667071, 1195203, 1268979, 1467763, 2013992, 2367906, and 3752948 and composite for all other n less than 8866397.
The Prime Pages keeps a list of the Top 20 Woodall Primes.
What is sieving?
Sieving is the first step to prime finding. In general, a sieve separates wanted/desired elements from unwanted material using a tool such as a mesh, net or other filtration or distillation methods. The word "sift" derives from this term. (Wikipedia - Sieve)
In PrimeGrid's case, the desired elements ultimately are prime numbers and the unwanted material are composite numbers. Our tool of choice for PPS sieve is Geoff Reynolds'/Ken Brazier's tpsieve program. It eliminates possible candidates by removing numbers that have small factors. As this process is much faster than primality testing, it is good to thoroughly sieve a data set before primality testing.
Sieving removes many candidates at the beginning. However, the deeper the sieve goes, the slower the rate of removal, till eventually sieving removes candidates at the same rate as primality testing. This is sometimes referred to as "optimal depth". Primality testing is recommended at this point.
There are many factors that determine how much time and how deep to sieve. After sieving, all the remaining candidates must be primality tested to determine their "prime" status.
32 bit OS with 64 bit CPU
This is for those who are "driving with the hand brake active" (running a 32 bit OS on a 64 bit machine) ;) Wubi is a very nice tool that installs Ubuntu as a dual boot to your 64 bit machine. It's as simple as adding a program to Windows. You can even uninstall it like you would any other program. :)
Wubi - Ubuntu Installer
After getting 64 bit OS running on your machine, here's a link to ALL BOINC clients (including Linux x64): http://boinc.berkeley.edu/download_all.php If you are new to Linux and need help getting set up, let us know.
It really is simple. :)
Ubuntu has a power save feature that throttles the CPU frequency down to save power. It does not treat BOINC as an active program so will throttle down thus causing under-performance. For those downloading the latest Ubuntu 11.04, please follow these directions to make sure the frequency is not throttled down while BOINC is running:
1. In Ubuntu, right click the top menu bar
2. Select add to panel
3. Select "CPU Frequency Scaling Monitor"
4. Click add
This will add a processor icon to the top menu. Click on the icon and set to "Performance". This also allows you to see the CPU frequency.
____________
|
|
|
|
|
|
Only 3 days to go, so starting to lower my buffer with PPS Sieves.
Hoping for my first top100 ranking ;)
____________
 |
|
|
 Crun-chiVolunteer tester
Send message
Joined: 25 Nov 09
Posts: 3101
ID: 50683
Credit: 72,155,825
RAC: 519
                       
|
|
Scoring Information
Scores will be kept for individuals and teams. Only work units issued AFTER 20 June 2011 17:16 UTC and received BEFORE 21 June 2011 17:16 UTC will be considered for credit. Since this is a fixed credit project, we'll be using cobblestones for scoring.
So if I made WU right now I will not get credit for it? |
|
|
rroonnaallddVolunteer developer
Volunteer tester
Send message
Joined: 3 Jul 09
Posts: 1213
ID: 42893
Credit: 34,634,263
RAC: 0
         
|
|
Only WUs in this time frame will get challenge points but every valid unit get credits granted.
____________
Best wishes. Knowledge is power. by jjwhalen
 |
|
|
Crun-chiVolunteer tester
Send message
Joined: 25 Nov 09
Posts: 3101
ID: 50683
Credit: 72,155,825
RAC: 519
|
|
Thanks for clarification! |
|
|
JohnHonorary cruncher
Send message
Joined: 21 Feb 06
Posts: 2875
ID: 2449
Credit: 2,681,934
RAC: 0
|
|
How to Join the Challenge
To participate in the Challenge, please select only the Cullen/Woodall Prime Search (Sieve) project in your PrimeGrid preferences section. Also, set "Send work from any subproject if selected projects have no work" to no to guarantee that no other work will be sent. The Challenge will begin 20 June 2011 17:16 UTC and end 21 June 2011 17:16 UTC. Application builds are available for the following:
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.01
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.12 (cuda23)
- Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU 1.12
- Linux running on an Intel x86-compatible CPU 1.12
- Linux running on an Intel x86-compatible CPU 1.12 (cuda23)
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.12
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.12 (cuda23)
- Mac OS 10.3 or later running on Motorola PowerPC 1.12
- Mac OS 10.4 or later running on Intel 1.12
- Mac OS 10.4 or later running on Intel 1.12 (cuda32)
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.12
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.12 (cuda32)
Note: 64 bit CPU builds benefit from a 1.7X speed advantage over 32 bit CPU...so 1.7X the credit. :)
Recommendation: The Cullen/Woodall (Sieve) application requires a one time download of a 15MB sieve file. Please consider running a few Cullen/Woodall (Sieve) WU's before the Challenge begins so your client will already have the sieve file. This way, bandwidth can be used to deliver WU's instead of the sieve file. :) Thank you!
Time zone converter:
The servers are located in the Northern Hemisphere; therefore, we'll observe summer. However, the Southern Hemisphere will be experiencing the Winter Solstice.
The World Clock - Time Zone Converter
NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section to the left of the countdown clock.
Scoring Information
Scores will be kept for individuals and teams. Only work units issued AFTER 20 June 2011 17:16 UTC and received BEFORE 21 June 2011 17:16 UTC will be considered for credit. Since this is a fixed credit project, we'll be using cobblestones for scoring.
Credit is currently set at 364.43 cobblestones per WU.
What to expect at Challenge start
The server always gets hit hard at the beginning of the Challenge. However, Cullen/Woodall (Sieve) tasks are quite long so we don't expect a heavy load. Nevertheless, a few hours before the start (20 June 2011 17:16 UTC) "max cache" will be dropped. Additionally, "max to send" will be dropped. Anyone attempting to request more will be met with "max cache" messages.
We'll raise the front page buffer before the start of the Challenge. These settings will be adjusted as necessary. Afterwards, as conditions allow, we'll raise "max cache". We'll continue to increase "max cache" when the server can handle it.
This method allows the greatest opportunity for the most clients to get work. Even if it's just 1 task for the first few minutes, at least the client is crunching. Past Challenges have shown that clients have an excellent chance to reach "max cache" before their first task is complete. We expect the same this time.
____________
|
|
|
|
|
|
Recommendation:
The Cullen/Woodall (Sieve) application requires a one time download of a 15MB sieve file.
Please consider running a few Cullen/Woodall (Sieve) WU's before the Challenge begins so your client will already have the sieve file.
This way, bandwidth can be used to deliver WU's instead of the sieve file. :)
Thank you!
Lennart |
|
|
|
|
|
Team Aggie The Pew are honing their several claws. As ever The Vermin Realm look forward to a great challenge and wish good fortune to all in it. |
|
|
|
|
|
All my GPU's are ATI so maybe when there is a ATI app for that project.
____________
Proud Founder of 
Have a look at my WebCam |
|
|
|
|
|
Why (and when) was the start of the race changed? It was initially listed to start at the 21st at 17:16 UTC if my memory doesn't betray me...
____________
|
|
|
JohnHonorary cruncher
Send message
Joined: 21 Feb 06
Posts: 2875
ID: 2449
Credit: 2,681,934
RAC: 0
|
Why (and when) was the start of the race changed? It was initially listed to start at the 21st at 17:16 UTC if my memory doesn't betray me...
The date was incorrect. It was changed shortly after the completion of the last challenge...so about a month ago.
____________
|
|
|
|
|
Why (and when) was the start of the race changed? It was initially listed to start at the 21st at 17:16 UTC if my memory doesn't betray me...
The date was incorrect. It was changed shortly after the completion of the last challenge...so about a month ago.
Thank you for the answer. I know it was one day late for the solstice but I thought that the admins had their reasons to start at the 21st. Let's hope you didn't caught too much crunchers off guard, especially those who only crunch PG during the challenges. It might be a good idea to stick to the schedules once they are out even if we miss a solstice by a day or two ;)
____________
|
|
|
Sysadm@NbgVolunteer moderator
Volunteer tester
Project scientist
Send message
Joined: 5 Feb 08
Posts: 1210
ID: 18646
Credit: 802,231,333
RAC: 183,377
                  
|
|
happy challenge
count me in
:D
____________
Sysadm@Nbg
my current lucky number: 113856050^65536 + 1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/
 |
|
|
|
|
|
Good Luck to all the GPU customers.
I'll be a mid-pack contender and will also do a few PPS LLR to keep the CPU on it's toes.
May as well use the opportunity to brag that I'm coming tie first!
____________
Warped
  |
|
|
|
|
|
Good luck to all participants.
This time I'll have my personal "challenge clean up" phase to get rid of the pink CW sieve badge that I'll aquire during the challenge :D
____________
|
|
|
|
|
Credit is currently set at 364.43 cobblestones per WU.
Is this for both the CPU and GPU tasks?
____________
Proud member of Team Aggie the Pew
"Wir müssen wissen. Wir werden wissen."
"We must know, we shall know."
- David Hilbert, 1930 |
|
|
|
|
Credit is currently set at 364.43 cobblestones per WU.
Is this for both the CPU and GPU tasks?
Yes. There is no difference between CPU and GPU tasks.
____________
|
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
           
|
|
A plea to all you GPU hogs: Take a break and let those of us with CPUs grab some WUs. The GPU machines are grabbing them so fast that the CPU machines (mine at least) keep getting "Nothing available ..." (except for the occasional single WU) from the server when we ask for tasks.
____________
Murphy (AtP)
 |
|
|
|
|
Credit is currently set at 364.43 cobblestones per WU.
Is this for both the CPU and GPU tasks?
Yes. There is no difference between CPU and GPU tasks.
Apart from the speed!
Holy Moly. Look at the leader-board already. My most advanced task is at less that 30%. ;-)
____________
Warped
|
|
|
|
|
Credit is currently set at 364.43 cobblestones per WU.
Is this for both the CPU and GPU tasks?
Yes. There is no difference between CPU and GPU tasks.
Apart from the speed!
Holy Moly. Look at the leader-board already. My most advanced task is at less that 30%. ;-)
Less than 22% here :D This afternoon I ran a set of WUs on my CPU: 3.5 hours per task per core. Time per WU on the 470: 135 seconds (official binaries!).
____________
|
|
|
|
|
A plea to all you GPU hogs: Take a break and let those of us with CPUs grab some WUs. The GPU machines are grabbing them so fast that the CPU machines (mine at least) keep getting "Nothing available ..." (except for the occasional single WU) from the server when we ask for tasks.
I got the same message at first, but I eventually got a task for each of my cores within about 15 minutes.
At this rate, I won't need any more for several hours anyway. |
|
|
|
|
A plea to all you GPU hogs: Take a break and let those of us with CPUs grab some WUs. The GPU machines are grabbing them so fast that the CPU machines (mine at least) keep getting "Nothing available ..." (except for the occasional single WU) from the server when we ask for tasks.
I got the same message at first, but I eventually got a task for each of my cores within about 15 minutes.
At this rate, I won't need any more for several hours anyway.
Yeah, that is my situation also. Usually, I run into a limit on my WU count at the beginning of a challenge. Do the GPU guys have a limit?
Jim
CPU only. |
|
|
|
|
A plea to all you GPU hogs: Take a break and let those of us with CPUs grab some WUs. The GPU machines are grabbing them so fast that the CPU machines (mine at least) keep getting "Nothing available ..." (except for the occasional single WU) from the server when we ask for tasks.
I got the same message at first, but I eventually got a task for each of my cores within about 15 minutes.
At this rate, I won't need any more for several hours anyway.
Yeah, that is my situation also. Usually, I run into a limit on my WU count at the beginning of a challenge. Do the GPU guys have a limit?
Jim
CPU only.
Yes.
____________
|
|
|
|
|
|
I had all my machines set to fetch additional work of 0.0 days and I still had 4 machines that took a good 3 minutes into the start to stop getting no work available messages. Also, it was indicated that it would restrict so all machines can get work but I don't think it worked out for everyone. At about 5 minutes in I raised all my machines to fetch additional 0.1 days but most of them got no work available messages. |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2577
ID: 29980
Credit: 548,740,837
RAC: 20,745
                      
|
|
GPU desktop lag, how much I don't miss you! 23 hours to go... |
|
|
|
|
|
this seems a waste of time... 3.5 hours in, and so far no wus (apart from the couple I had before)...
if I don't get some soon, I'm going back to normal... |
|
|
|
|
this seems a waste of time... 3.5 hours in, and so far no wus (apart from the couple I had before)...
if I don't get some soon, I'm going back to normal...
Not completely sure on this BUT by looking at what you are running, you have a cache full of pps sieves right now and those will some times run before the cw sieves. If you want to participate in the challenge, you might want to insure your preferences are set for cw sieves only with no pps sieves, abort the pps sieves and let your system get some cw work. This is of course assuming you want to run your gpu.
Rick
____________
@AggieThePew
 |
|
|
VatoVolunteer tester
Send message
Joined: 2 Feb 08
Posts: 812
ID: 18447
Credit: 490,627,587
RAC: 222,321
            
|
|
I'm only doing this to get the last few credits for Pink on CW Sieve - I'm mostly CPU - and then I'm done on this subproject. It took 10 mins to get work for all my hosts. Not that bad considering those hungry GPUs were clamouring for food... :-)
____________
 |
|
|
|
|
|
I've increased from 5 to 7 days, and suspended all other work, including PPS sieves... still nothing... |
|
|
|
|
|
It's been over 2 hrs.since the start of the challenge and I've yet to get a single WU on this Linux box. I completed 4 last night to make sure I had the master file see how long they took on this box (~3hrs. 10 min.). My 3 Win7 boxes got work.
http://www.primegrid.com/show_host_detail.php?hostid=170863
What might I be doing wrong? I haven't changed any settings since last night except allowing new tasks and increasing the cache from 0 to .25days.
One odd thing I see is the time in the message log starts (incorrectly) at 5:21PM, then is suddenly at the correct time, 1:22PM. I've never seen that before.
Mon 20 Jun 2011 05:21:45 PM EDT Starting BOINC client version 6.10.17 for x86_64-pc-linux-gnu
Mon 20 Jun 2011 05:21:45 PM EDT log flags: file_xfer, sched_ops, task
Mon 20 Jun 2011 05:21:45 PM EDT Libraries: libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Mon 20 Jun 2011 05:21:45 PM EDT Data directory: /var/lib/boinc-client
Mon 20 Jun 2011 05:21:45 PM EDT Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz [Family 6 Model 23 Stepping 10]
Mon 20 Jun 2011 05:21:45 PM EDT Processor: 6.00 MB cache
Mon 20 Jun 2011 05:21:45 PM EDT Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse
Mon 20 Jun 2011 05:21:45 PM EDT OS: Linux: 2.6.32-32-generic
Mon 20 Jun 2011 05:21:45 PM EDT Memory: 3.84 GB physical, 11.24 GB virtual
Mon 20 Jun 2011 05:21:45 PM EDT Disk: 227.45 GB total, 211.37 GB free
Mon 20 Jun 2011 05:21:45 PM EDT Local time is UTC -4 hours
Mon 20 Jun 2011 05:21:45 PM EDT No usable GPUs found
Mon 20 Jun 2011 05:21:45 PM EDT Not using a proxy
Mon 20 Jun 2011 05:21:45 PM EDT eon2 URL http://eon.ices.utexas.edu/eon2/; Computer ID 4652; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT DNETC@HOME URL http://dnetc.net/; Computer ID 18418; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT Milkyway@home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 232026; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5599073; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT World Community Grid URL http://www.worldcommunitygrid.org/; Computer ID 1406774; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT AQUA@home URL http://aqua.dwavesys.com/; Computer ID 73896; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT PrimeGrid URL http://www.primegrid.com/; Computer ID 170863; resource share 100
Mon 20 Jun 2011 05:21:45 PM EDT Reading preferences override file
Mon 20 Jun 2011 05:21:45 PM EDT Preferences limit memory usage when active to 3142.41MB
Mon 20 Jun 2011 05:21:45 PM EDT Preferences limit memory usage when idle to 3535.21MB
Mon 20 Jun 2011 05:21:46 PM EDT Preferences limit disk usage to 10.00GB
Mon 20 Jun 2011 01:22:08 PM EDT PrimeGrid work fetch resumed by user
Mon 20 Jun 2011 01:22:10 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:24:49 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:35:03 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:35:27 PM EDT Reading preferences override file
Mon 20 Jun 2011 01:35:27 PM EDT Preferences limit memory usage when active to 3142.41MB
Mon 20 Jun 2011 01:35:27 PM EDT Preferences limit memory usage when idle to 3535.21MB
Mon 20 Jun 2011 01:35:27 PM EDT Preferences limit disk usage to 10.00GB
Mon 20 Jun 2011 01:37:12 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:37:19 PM EDT Reading preferences override file
Mon 20 Jun 2011 01:37:19 PM EDT Preferences limit memory usage when active to 3142.41MB
Mon 20 Jun 2011 01:37:19 PM EDT Preferences limit memory usage when idle to 3535.21MB
Mon 20 Jun 2011 01:37:19 PM EDT Preferences limit disk usage to 10.00GB
Mon 20 Jun 2011 01:37:39 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:44:02 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:44:04 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:55:33 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:57:55 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:58:31 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:59:13 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 01:59:31 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 02:24:07 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 02:24:13 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 02:24:13 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 02:24:14 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:04:28 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:04:28 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:04:29 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:04:29 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:08:59 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:20:59 PM EDT PrimeGrid update requested by user
Mon 20 Jun 2011 03:24:13 PM EDT Reading preferences override file
Mon 20 Jun 2011 03:24:13 PM EDT Preferences limit memory usage when active to 3142.41MB
Mon 20 Jun 2011 03:24:13 PM EDT Preferences limit memory usage when idle to 3535.21MB
Mon 20 Jun 2011 03:24:13 PM EDT Preferences limit disk usage to 10.00GB
Mon 20 Jun 2011 03:24:48 PM EDT PrimeGrid work fetch suspended by user
Mon 20 Jun 2011 03:24:49 PM EDT PrimeGrid work fetch resumed by user
Mon 20 Jun 2011 03:27:07 PM EDT PrimeGrid update requested by user
|
|
|
|
|
I've increased from 5 to 7 days, and suspended all other work, including PPS sieves... still nothing...
Someone more experienced might be able to make sure of this but I've seen Boinc stop getting work if you suspend jobs. For some reason even if you've suspended individual jobs boinc thinks you no longer want any jobs so it will not try to get jobs like normal.
Rick
____________
@AggieThePew
|
|
|
|
|
I've increased from 5 to 7 days, and suspended all other work, including PPS sieves... still nothing...
A project won't download WU's if you have any suspended. |
|
|
|
|
I've increased from 5 to 7 days, and suspended all other work, including PPS sieves... still nothing...
Someone more experienced might be able to make sure of this but I've seen Boinc stop getting work if you suspend jobs. For some reason even if you've suspended individual jobs boinc thinks you no longer want any jobs so it will not try to get jobs like normal.
Rick
Strange I've always gotten the opposite response from BOINC. If I suspend some tasks for a project it turns around and fetches more tasks for that project. |
|
|
|
|
|
I rebooted the Linux box, it's getting work now. Grrr.
Some days I hate computers. |
|
|
|
|
Strange I've always gotten the opposite response from BOINC. If I suspend some tasks for a project it turns around and fetches more tasks for that project.
LOL you have a special program :)
____________
@AggieThePew
|
|
|
|
|
Strange I've always gotten the opposite response from BOINC. If I suspend some tasks for a project it turns around and fetches more tasks for that project.
LOL you have a special program :)
Newest x86_64 linux version 6.10.58 but it did that going back to 6.2.14 for me.
I use to mess with it a lot for the BOINC project that I admin until we corrected priority on resends for instance. |
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
|
I've increased from 5 to 7 days, and suspended all other work, including PPS sieves... still nothing...
You must not Suspend ANY PrimeGrid Tasks or you will never fetch new work -- I increase the number of days in my cache (one day at a time) until I get the needed WUs (then suspend the unwanted Tasks).
____________
Murphy (AtP)
|
|
|
|
|
I've increased from 5 to 7 days, and suspended all other work, including PPS sieves... still nothing...
You must not Suspend ANY PrimeGrid Tasks or you will never fetch new work -- I increase the number of days in my cache (one day at a time) until I get the needed WUs (then suspend the unwanted Tasks).
That's a good strategy. I will try that.
|
|
|
|
|
|
Not a good strategy if you're running both CPU and GPU as in this sub-project, you'll hit the max WU's per host with GPU WU's before the cache hits 3 days. |
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
|
Not a good strategy if you're running both CPU and GPU as in this sub-project, you'll hit the max WU's per host with GPU WU's before the cache hits 3 days.
If you have that fast of a GPU, the CPU is not relevant anyway! ROFL
____________
Murphy (AtP)
|
|
|
|
|
|
i keep getting 27 hr wu's i understood they supposed to be 4hrs |
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
|
i keep getting 27 hr wu's i understood they supposed to be 4hrs
That is just a [BAD] estimate. After you crunch them for a while, you will see that they adjust to anywhere from 3.5 to 9 hours (depending on CPU speed).
____________
Murphy (AtP)
|
|
|
|
|
i keep getting 27 hr wu's i understood they supposed to be 4hrs
That is just a [BAD] estimate. After you crunch them for a while, you will see that they adjust to anywhere from 3.5 to 9 hours (depending on CPU speed).
Normally they adjust but so far most of my machines no matter how many cores or how fast they complete work get new ones estimated at 27 or 36 hours. It's really absurd. |
|
|
|
|
|
We started an upgrade for our GPU server just shortly (like, minutes)
before the start of the Challenge. Boinc now reports
20-Jun-2011 23:29:19 [---] NVIDIA GPU 0: Tesla C2070 (driver version unknown,
CUDA version 4000, compute capability 2.0, 4096MB, 1028 GFLOPS peak)
20-Jun-2011 23:29:19 [---] NVIDIA GPU 1: Tesla C2070 (driver version unknown,
CUDA version 4000, compute capability 2.0, 4096MB, 1028 GFLOPS peak)
20-Jun-2011 23:29:19 [---] NVIDIA GPU 2: Tesla C2050 (driver version unknown,
CUDA version 4000, compute capability 2.0, 3072MB, 1028 GFLOPS peak)
20-Jun-2011 23:29:19 [---] NVIDIA GPU 3 (not used): Tesla C2050 (driver version unknown,
CUDA version 4000, compute capability 2.0, 2687MB, 1028 GFLOPS peak)
The old C2050's have been running very well with "driver version unknown",
but there were new "updated" drivers loaded along with the two new cards.
Both CW_sieve and PPS_sieve now give immediate errors, so instead of
doubling my rate (or 1.5'ing my rate, if the 4th card won't be used),
I've dropped it to zero. Most likely too late to get much of a contribution
on the Challenge, but I'd appreciate hearing if anyone has a suggestion.
It's not my personal machine, so I don't have the option of installing
old drivers.
-Bruce* |
|
|
|
|
We started an upgrade for our GPU server just shortly (like, minutes)
before the start of the Challenge. Boinc now reports
20-Jun-2011 23:29:19 [---] NVIDIA GPU 0: Tesla C2070 (driver version unknown,
CUDA version 4000, compute capability 2.0, 4096MB, 1028 GFLOPS peak)
20-Jun-2011 23:29:19 [---] NVIDIA GPU 1: Tesla C2070 (driver version unknown,
CUDA version 4000, compute capability 2.0, 4096MB, 1028 GFLOPS peak)
20-Jun-2011 23:29:19 [---] NVIDIA GPU 2: Tesla C2050 (driver version unknown,
CUDA version 4000, compute capability 2.0, 3072MB, 1028 GFLOPS peak)
20-Jun-2011 23:29:19 [---] NVIDIA GPU 3 (not used): Tesla C2050 (driver version unknown,
CUDA version 4000, compute capability 2.0, 2687MB, 1028 GFLOPS peak)
The old C2050's have been running very well with "driver version unknown",
but there were new "updated" drivers loaded along with the two new cards.
Both CW_sieve and PPS_sieve now give immediate errors, so instead of
doubling my rate (or 1.5'ing my rate, if the 4th card won't be used),
I've dropped it to zero. Most likely too late to get much of a contribution
on the Challenge, but I'd appreciate hearing if anyone has a suggestion.
It's not my personal machine, so I don't have the option of installing
old drivers.
-Bruce*
I see "driver version unknown" here too, regardless of the used driver version (currently 275.09.07 on a Debian Squeeze installation, though I'm using Windows for the challenge because of the insane overclocking potential my 470 has). Have you checked for missing libraries (ldd)? Did you try to manually start the (BOINC) binaries on the various cards? I have no problems here with NVIDIAs newest drivers running "old" CUDA 2.3 code but I don't know if the Teslas are delivered with special drivers which might behave different.
Edit: Corrected the driver version.
____________
|
|
|
|
|
i keep getting 27 hr wu's i understood they supposed to be 4hrs
That is just a [BAD] estimate. After you crunch them for a while, you will see that they adjust to anywhere from 3.5 to 9 hours (depending on CPU speed).
As little as 1hr. 38min. on an i5-200K @ 4.09Ghz ;)
|
|
|
|
|
|
Still position 154 after 6.5 hours with the box shut down (planned)... not that bad...
____________
|
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2577
ID: 29980
Credit: 548,740,837
RAC: 20,745
|
|
Just how much power is being run out there? I'm running two modern-ish GPUs and one older one so I thought I'd have a good run at this, but I've been slipping down the rankings continuously and wonder if I can even hang onto a top100 position by the end. I didn't run many CPUs this time unless they were in the GPU boxes anyway since they seem so insignificant, but now wonder if I should of... |
|
|
|
|
|
I unsuspended to draw down work and got rid of lots of PPS Sieve... then tried again, and got lots of CW Sieve work...
Thank you folks...
Pity there's not a competition for those of us with only one computer! ;) |
|
|
|
|
Just how much power is being run out there? I'm running two modern-ish GPUs and one older one so I thought I'd have a good run at this, but I've been slipping down the rankings continuously and wonder if I can even hang onto a top100 position by the end. I didn't run many CPUs this time unless they were in the GPU boxes anyway since they seem so insignificant, but now wonder if I should of...
You probably need one of those RenderStream boards with 8 GTX 580s in the PCIe slots... should be enough for the top 100 during the winter solstice challenge :D
____________
|
|
|
|
|
|
Not sure if anyone else has mentioned this but thanks to the admins and powers that be. The server and pg seem to be running really well during this challenge. Even the message boards didn't slow or drag during this one.
Great job.
____________
@AggieThePew
|
|
|
|
|
Just how much power is being run out there? I'm running two modern-ish GPUs and one older one so I thought I'd have a good run at this, but I've been slipping down the rankings continuously and wonder if I can even hang onto a top100 position by the end. I didn't run many CPUs this time unless they were in the GPU boxes anyway since they seem so insignificant, but now wonder if I should of...
I slid from 71st yesterday afternoon to 91st now using 1 GTX-570 and 4 CPU's. I'm pretty happy with that, considering how many people seem to have multiple GPU's, even in 1 rig. |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2577
ID: 29980
Credit: 548,740,837
RAC: 20,745
|
|
Not as bad as I feared, 79th place as of last update. So unless anyone did a big dump in the last seconds I doubt that'll change much.
Now I can look forward to my systems winding down so my house can cool off again :) And no more GPU lag... |
|
|
JohnHonorary cruncher
Send message
Joined: 21 Feb 06
Posts: 2875
ID: 2449
Credit: 2,681,934
RAC: 0
|
|
The results are Final!
The Summer Solstice has arrived in the Northern Hemisphere. We hope everyone enjoys this longest day of the year...and for you Southern Hemisphere folks, we hope you kept warm. :)
This was a unique challenge in that the tasks were exceptionally short. It wasn't planned this way, but the server survived with no problems. The fastest tasks came in under 2 minutes, by far our most demanding Challenge yet. The new Memcached host configuration proved to be exceptional. :)
The Cullen/Woodall (Sieve) reached an incomplete depth of over 566T. Over 30T of sieve work was crunched in 251K tasks resulting in over 91.5M cobblestones awarded. 147 teams and 811 individuals participated in the Challenge.
The Challenge Points stats will be updated soon. Congratulations to Sicituradastra. as the top team and Ross* as the top individual. Remember, the top 100 individual and top 50 team places earn points for this Challenge.
Thank you again to everyone. We appreciate your participation and hope you had fun! Have a wonderful summer and we look forward to seeing you in a couple months at the next Challenge - The Dog Days of Summer Challenge - 26-28 August - 48 hours on the PPS (LLR) application! Come take a break from the Dog Days and cool off with a few primes. It's a GREAT opportunity for you to find a Top 5000 Prime. :)
SPECIAL NOTE: We're entering "summer hours" at PrimeGrid which means you may notice longer response times to questions and issues. Fortunately, with such a knowledgeable user base, y'all won't notice us missing in the forum. ;) We'll make sure to load the buffers with extra work. We are still around...just not as much. Have a GREAT summer!!!
Stats: Participants | Teams
Top 10 Teams
1 Sicituradastra. 14753596.90
2 SETI.Germany 12503604.13
3 SETI.USA 9408133.03
4 Team 2ch 5786788.98
5 Czech National Team 4779139.16
6 The Knights Who Say Ni! 3040806.55
7 Polish National Team 3018576.30
8 BOINCstats 2656697.00
9 Ishtar 2345109.08
10 PrimeSearchTeam 2334540.60
Top 10 Individuals
1 Ross* Sicituradastra. 4326516.71
2 Carat@voice Team 2ch 2939130.50
3 IshtarIS Ishtar 2345109.08
4 [SG]marodeur6 SETI.Germany 1995255.98
5 ThrasherX-17 Keep The Fire Alive! 1553566.44
6 Snf* Sicituradastra. 1424558.10
7 tng* Sicituradastra. 1388843.93
8 Cruncher Pete.SETI.USA SETI.USA 1231045.61
9 HSchmirPo SETI.Germany 1216468.39
10 Siegfried Niklas Crunching Family 1197153.59
____________
|
|
|
yank
Send message
Joined: 14 May 07
Posts: 111
ID: 8367
Credit: 11,474,819,218
RAC: 0
         
|
|
Well done Team Sicituradastra. The top team in three of this year's challenges. WOW |
|
|
JohnHonorary cruncher
Send message
Joined: 21 Feb 06
Posts: 2875
ID: 2449
Credit: 2,681,934
RAC: 0
|
|
The next Challenge in August will be on PPS (LLR). This project has recently entered into a new phase in its search for proth primes. To follow progress on this project, please see: PPS (LLR) Milestones, Goals, and Progress
If you wish to participate, please select Proth Prime Search (LLR) in you PrimeGrid preferences page.
NOTE: SGS (LLR) is still a priority as well. We are still looking for a Sophie Germain prime or a twin prime. :)
____________
|
|
|
|
|
We started an upgrade for our GPU server just shortly (like, minutes)
before the start of the Challenge. Boinc now reports
[code]
20-Jun-2011 23:29:19 [---] NVIDIA GPU 0: Tesla C2070 (driver version unknown,
CUDA version 4000, compute capability 2.0, 4096MB, 1028 GFLOPS peak)
...
-Bruce*
I see "driver version unknown" here too, regardless of the used driver version (currently 275.09.07 on a Debian Squeeze installation,
OK, I now have
nvidia-smi -q
reporting " Driver Version : 275.09.07"
same as what you have. Seems to suggest that it's not a problem
of the driver version?
For libraries, I get
ls /lib/libc.so.*
/lib/libc.so.6
and lib and lib64 have links to
so.3.1.9
Thanks, Bruce*
though I'm using Windows for the challenge because of the insane overclocking potential my 470 has). Have you checked for missing libraries (ldd)? Did you try to manually start the (BOINC) binaries on the various cards? I have no problems here with NVIDIAs newest drivers running "old" CUDA 2.3 code but I don't know if the Teslas are delivered with special drivers which might behave different.
Edit: Corrected the driver version.
|
|
|
|
|
I see "driver version unknown" here too, regardless of the used driver version (currently 275.09.07 on a Debian Squeeze installation,
Driver version unknown is a known bug in linux boinc. It doesn't matter what version of the client or the server is running. The latest stable release, 6.10.58, has a number of GPU bugs that in theory are fixed in 6.10.60. Apparently that version has already been released and marked old for windows but never came to linux. It doesn't actually impact your ability to compute in most projects. It only can be a problem in a project with a custom gpu app plan that checks minimum version numbers for cuda compute capabilities (or OpenCL) and doesn't realize linux is broken. |
|
|
|
|
|
congrads very good love these site very large universe |
|
|
|
|
|
I am sure I am not the only member who allowed the "Birthday" part of the challenge to go unnoticed. PG turned 6 years old on 12 June 2011 and the project continues to be a spectacular success.
Thanks go to all the people who make this possible, the volunteer developers (Rogue, Ken_g6 etc), the testers and especially to Rytis, John and Lennart.
Here’s to the next 6 years.
____________
Warped
|
|
|
|
|
Well done Team Sicituradastra. The top team in three of this year's challenges. WOW
Thank you Yank ;-))
I also want to say thanx to the wonderful guys in this team.. - and that is...
..in fact.. they are all wonderful! ;-) LoL
What a blessed coconut I am. ;-)))
____________
   |
|
|
|
|
|
Well done, western world!
GPU challenges are so damn good! I hope next year it will be more than 2 GPU challenges.
I'll be back...
____________
  |
|
|
|
|
I see "driver version unknown" here too, regardless of the used driver version (currently 275.09.07 on a Debian Squeeze installation,
Driver version unknown is a known bug in linux boinc. It doesn't matter what version of the client or the server is running. The latest stable release, 6.10.58, has a number of GPU bugs that in theory are fixed in 6.10.60. Apparently that version has already been released and marked old for windows but never came to linux. It doesn't actually impact your ability to compute in most projects. It only can be a problem in a project with a custom gpu app plan that checks minimum version numbers for cuda compute capabilities (or OpenCL) and doesn't realize linux is broken.
Not sure why the C2050's would have worked before, but no longer do.
Deleting everything and picking up new Primegrid files didn't help. The
computation error says
version 6.10.58 process exited with code 1 (0x1 -255)
meanwhile, my RAC is dropping like a stone, after 5 months with
the two c2050's. Any suggestions will be appreciated.
Bruce* |
|
|
|
|
I see "driver version unknown" here too, regardless of the used driver version (currently 275.09.07 on a Debian Squeeze installation,
Driver version unknown is a known bug in linux boinc. It doesn't matter what version of the client or the server is running. The latest stable release, 6.10.58, has a number of GPU bugs that in theory are fixed in 6.10.60. Apparently that version has already been released and marked old for windows but never came to linux. It doesn't actually impact your ability to compute in most projects. It only can be a problem in a project with a custom gpu app plan that checks minimum version numbers for cuda compute capabilities (or OpenCL) and doesn't realize linux is broken.
Not sure why the C2050's would have worked before, but no longer do.
Deleting everything and picking up new Primegrid files didn't help. The
computation error says
version 6.10.58 process exited with code 1 (0x1 -255)
meanwhile, my RAC is dropping like a stone, after 5 months with
the two c2050's. Any suggestions will be appreciated.
Bruce*
Did you try to run the (non-boinc) sieve app manually (on every device) like this?
./tpsieve-cuda-x86_64-linux -p 100000e9 -P 100001e9 -k 3 -K 9999 -n 2M -N 3M -c60 -d DEVICE
This is a short test range I use when playing around with "my" experimental version - Runtime is around 64 seconds with the default apps and 54 seconds with my 32 bit binary on a GTX 470 @ stock clocks. Result should be: 173 factors found.
You can also try to start the non-boinc binary on several GPUs simultaneously, like:
./tpsieve-cuda-x86_64-linux -p 100000e9 -P 100001e9 -k 3 -K 9999 -n 2M -N 3M -c60 -t THREADS
---
I'm not sure if BOINC or the mixed GPU setup causes the problems... or a combination of the two...
____________
|
|
|
|
|
|
You can download the non-boinc versions here:
http://sites.google.com/site/kenscode/prime-programs
____________
|
|
|
|
|
You can download the non-boinc versions here:
http://sites.google.com/site/kenscode/prime-programs
Thanks, I'll have a look. -bd* |
|
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 928
ID: 3110
Credit: 234,161,304
RAC: 122,249
          
|
Not sure why the C2050's would have worked before, but no longer do.
Deleting everything and picking up new Primegrid files didn't help. The
computation error says
version 6.10.58 process exited with code 1 (0x1 -255)
meanwhile, my RAC is dropping like a stone, after 5 months with
the two c2050's. Any suggestions will be appreciated.
Bruce*
Most unusual. There are only a few situations where exit code 1 is still used. And all of them are supposed to print some error message to stderr.txt before exiting.
____________
|
|
|
|
|
You can download the non-boinc versions here:
http://sites.google.com/site/kenscode/prime-programs
From the tarfile with the source, I cd to pps, then
make non-boinc
appears to compile with
NVCC = /usr/local.hide/cuda/bin/nvcc
LD32 = $(NVCC) -m32
LD64 = $(NVCC) -m64
after editing to point to our nonstandard nvcc location, but I get
./tpsieve-cuda-x86-linux: error while loading shared libraries: libcudart.so.3
that's most likely because we have the link to so.3 in either
/usr/local.hide/lib
or
/usr/local.hide/lib64
Neither of
LD32 = /usr...
or
LD32 = /usr... -m32
compile, with an early error message. My previous CUDA
compiling experience is with msieve (over on mersenneforum),
which has lines like
CUDA_INC_DIR = /usr/local/cuda/include
CUDA_LIB_DIR = /usr/local/cuda/lib64
CFLAGS += -I"$(CUDA_INC_DIR)" -DHAVE_CUDA
# Also, the CUDA driver library has a different name in linux
# LIBS += "$(CUDA_LIB_DIR)/cuda.lib"
LIBS += -lcuda
for additional nonstandard locations. I see things like
BOINC_LOAD_LIBS
in the part of the tpsieve makefile that does the boinc version,
but not in the non-boinc part. Perhaps I ought to PM geoff over
on the 'forum (another long time member there ...).
@admin: this thread likely ought to be relocated somewhere
more appropriate?
|
|
|
|
|
after editing to point to our nonstandard nvcc location, but I get
./tpsieve-cuda-x86-linux: error while loading shared libraries: libcudart.so.3
that's most likely because we have the link to so.3 in either
/usr/local.hide/lib
or
/usr/local.hide/lib64
For a quick test you should be able to start the binary without messing with the linker configuration with
32 bit:
LD_LIBRARY_PATH=/path/to/the/cuda/libs ./tpsieve-cuda-x86-linux
64 bit:
LD_LIBRARY_PATH=/path/to/the/cuda/libs ./tpsieve-cuda-x86_64-linux
The long version (in case the above command line doesn't work):
32 bit:
LD_LIBRARY_PATH=/path/to/the/cuda/libs:$LD_LIBRARY_PATH ./tpsieve-cuda-x86-linux
64 bit:
LD_LIBRARY_PATH=/path/to/the/cuda/libs:$LD_LIBRARY_PATH ./tpsieve-cuda-x86_64-linux
Replace the /path/to/the/cuda/libs with the appropriate location. I installed the toolkit under /usr/local/cuda/ so in my case the path to the libraries is:
/usr/local/cuda/lib (32 bit) or /usr/local/cuda/lib64 (64 bit)
____________
|
|
|
|
|
For a quick test you should be able to start the binary without messing with the linker configuration with
64 bit:
LD_LIBRARY_PATH=/path/to/the/cuda/libs:$LD_LIBRARY_PATH ./tpsieve-cuda-x86_64-linux
This one worked, I think, sort-of:
LD_LIBRARY_PATH=/usr/local.hide/cuda/lib64:$LD_LIBRARY_PATH
./tpsieve-cuda-x86_64-linux -p 100000e9 -P 100001e9 -k 3 -K 9999 -n 2M -N 3M -c60 -t 4
tpsieve version cuda-0.2.3b (testing)
Compiled Jun 25 2011 with GCC 4.1.2 20080704 (Red Hat 4.1.2-48)
nstart=2000000, nstep=34
nstep changed to 32
tpsieve initialized: 3 <= k <= 9999, 2000000 <= n < 3000000
Sieve started: 100000000000000 <= p < 100001000000000
Thread 0 starting
Thread 1 starting
Thread 2 starting
Thread 3 starting
Detected GPU 1: Tesla C2070
Detected compute capability: 2.0
Detected 14 multiprocessors.
Detected GPU 3: Tesla C2050
Detected compute capability: 2.0
Detected 14 multiprocessors.
Detected GPU 0: Tesla C2070
Detected compute capability: 2.0
Detected 14 multiprocessors.
Detected GPU 2: Tesla C2050
Detected compute capability: 2.0
Detected 14 multiprocessors.
Computation Error: no candidates found for p=100000762311649.
Thread 0 completed
Waiting for threads to exit
Thread 2 completed
Thread 3 completed
Thread 1 completed
Sieve complete: 100000000000000 <= p < 100001000000000
Found 0 factors
count=31019409,sum=0x284af85735fd771f
Elapsed time: 15.42 sec. (0.02 init + 15.40 sieve) at 64939957 p/sec.
Processor time: 5.10 sec. (0.02 init + 5.08 sieve) at 197051081 p/sec.
Average processor utilization: 1.03 (init), 0.33 (sieve)
At least there's an error message. -Bruce*
|
|
|
|
|
|
Does
LD_LIBRARY_PATH=/usr/local.hide/cuda/lib64:$LD_LIBRARY_PATH
./tpsieve-cuda-x86_64-linux -p 100000e9 -P 100001e9 -k 3 -K 9999 -n 2M -N 3M -c60 -t 1 -d X
work? X = 1,2,3 or 4 // one card of the 4(?) in the box...
____________
|
|
|
|
|
Does
LD_LIBRARY_PATH=/usr/local.hide/cuda/lib64:$LD_LIBRARY_PATH
./tpsieve-cuda-x86_64-linux -p 100000e9 -P 100001e9 -k 3 -K 9999 -n 2M -N 3M -c60 -t 1 -d X
work? X = 1,2,3 or 4 // one card of the 4(?) in the box...
No, doesn't look like it --- no error message, but no factors found
either (much less 73). -Bruce*
-t 1 -d 2
tpsieve version cuda-0.2.3b (testing)
Compiled Jun 25 2011 with GCC 4.1.2 20080704 (Red Hat 4.1.2-48)
nstart=2000000, nstep=34
nstep changed to 32
tpsieve initialized: 3 <= k <= 9999, 2000000 <= n < 3000000
Sieve started: 100000000000000 <= p < 100001000000000
Thread 0 starting
Detected GPU 2: Tesla C2050
Detected compute capability: 2.0
Detected 14 multiprocessors.
Thread 0 completed
Waiting for threads to exit
Sieve complete: 100000000000000 <= p < 100001000000000
Found 0 factors
count=31019409,sum=0x284af85735fd771f
Elapsed time: 58.21 sec. (0.02 init + 58.19 sieve) at 17186248 p/sec.
Processor time: 4.33 sec. (0.02 init + 4.30 sieve) at 232341768 p/sec.
Average processor utilization: 1.08 (init), 0.07 (sieve)
---
LD_LIBRARY_PATH=/usr/local.hide/cuda/lib64:$LD_LIBRARY_PATH ./tpsiev
e-cuda-x86_64-linux -p 100000e9 -P 100001e9 -k 3 -K 9999 -n 2M -N 3M -c60 -t 1 -d 0
tpsieve version cuda-0.2.3b (testing)
Compiled Jun 25 2011 with GCC 4.1.2 20080704 (Red Hat 4.1.2-48)
nstart=2000000, nstep=34
nstep changed to 32
tpsieve initialized: 3 <= k <= 9999, 2000000 <= n < 3000000
Sieve started: 100000000000000 <= p < 100001000000000
Thread 0 starting
Detected GPU 0: Tesla C2070
Detected compute capability: 2.0
Detected 14 multiprocessors.
Thread 0 completed
Waiting for threads to exit
Sieve complete: 100000000000000 <= p < 100001000000000
Found 0 factors
count=31019409,sum=0x284af85735fd771f
Elapsed time: 58.25 sec. (0.02 init + 58.23 sieve) at 17175351 p/sec.
Processor time: 4.48 sec. (0.02 init + 4.46 sieve) at 224418059 p/sec.
Average processor utilization: 1.02 (init), 0.08 (sieve)
|
|
|
|
|
|
The only time when I saw something similar was when I tried to compile the tpsieve sources with the CUDA 3.1 SDK. That did never work here. The programs found no factors and slowed down to a crawl. In your case the cards/the tpsieve binary seems to run at full speed but nonetheless something else doesn't work here.
The bug hunt continues...
____________
|
|
|
|
|
|
Please update the PDF's with the new points. |
|
|
|
|
Please update the PDF's with the new points.
2nded. |
|
|
|
|
|
@ Admins...
Why isnt the Challenge standings updated Yet??
What can possibly be so difficult - that it takes 7 Weeks! to do it?
Come on, guys. When people follow up and crunch the challenges,
shouldnt the admins follow up such a minor job as to add in those numbers
on the standing list? ;-) Its only 18 days until the Next challenge start.
Or maybe its forgotten... ;-p
Anyone wanna bet? ;-))
____________
|
|
|
|
|
|
I'll just post this to save an admin some typing...
Remember it's summer hours at Primegrid
:)
____________
 |
|
|
|
|
I'll just post this to save an admin some typing...
Remember it's summer hours at Primegrid
:)
Sure, except the competition ended June 20th and we've had PSA credit updates since then so someone is around :) |
|
|
|
|
|
..I have summertime too. ;-)) Im not in a coma because of it.. lol
____________
|
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
|
..I have summertime too. ;-)) Im not in a coma because of it.. lol
I am ... but it may just be the heat!
____________
Murphy (AtP)
|
|
|
|
|
..I have summertime too. ;-)) Im not in a coma because of it.. lol
I am ... but it may just be the heat!
Yes, I think it is our hottest summer here. Dallas, Texas, USA has been hitting 110F (43C.) Last week we had a day where power was blacked out to a lot of things in the state so the power grid didn't collapse. |
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
|
..I have summertime too. ;-)) Im not in a coma because of it.. lol
I am ... but it may just be the heat!
Yes, I think it is our hottest summer here. Dallas, Texas, USA has been hitting 110F (43C.) Last week we had a day where power was blacked out to a lot of things in the state so the power grid didn't collapse.
If it stays above 100 thru Friday (and I would not put any money against that bet), then we will break 1980's record of 42 consecutive days above 100.
I'm in the Dallas area, too.
____________
Murphy (AtP)
|
|
|
Sysadm@NbgVolunteer moderator
Volunteer tester
Project scientist
Send message
Joined: 5 Feb 08
Posts: 1210
ID: 18646
Credit: 802,231,333
RAC: 183,377
|
|
please send us the heat!
I would like to have a real summer in summer
Here in Germany it's like in the fall.
An arctic breeze blowing through my office.
I'm about to crank up the heater.
____________
Sysadm@Nbg
my current lucky number: 113856050^65536 + 1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/
|
|
|
|
|
please send us the heat!
I would like to have a real summer in summer
Here in Germany it's like in the fall.
An arctic breeze blowing through my office.
I'm about to crank up the heater.
Please take it! Along with my energy bills that are 3-5 times higher in the summer from cooling. :)
Fall here is warmer than Norway's summer and you can have Fall too :) |
|
|
mfbabb2Volunteer tester
Send message
Joined: 10 Oct 08
Posts: 510
ID: 30360
Credit: 14,545,297
RAC: 34,787
|
please send us the heat!
I would like to have a real summer in summer
Here in Germany it's like in the fall.
An arctic breeze blowing through my office.
I'm about to crank up the heater.
Please take it! Along with my energy bills that are 3-5 times higher in the summer from cooling. :)
Fall here is warmer than Norway's summer and you can have Fall too :)
As a matter of fact, it is not unusual for our (Dallas, TX, USA) temps to be in the 80's F even in December (although only a few days hopefully).
We are about to break the 1980 record of 42 straight days above 100 F.
And a lot of those days have been between 105 and 110 (actual temp, not heat index).
____________
Murphy (AtP)
|
|
|
|
|
As a matter of fact, it is not unusual for our (Dallas, TX, USA) temps to be in the 80's F even in December (although only a few days hopefully).
We are about to break the 1980 record of 42 straight days above 100 F.
And a lot of those days have been between 105 and 110 (actual temp, not heat index).
Wow Murphy, that would be too many 100 degree days for me . Most of the eastern half of the USA has been extra hot this summer but Texas seems to have gotten an extra dose of heat and very little rain.
For our "cool" comparison in Raleigh, NC, USA
* broke (tied according to one source) the record for consecutive 100 degree days at 5
* tied record for highest temp at 105
* hottest July ever
* on track to break record for most 90+ degree days (91 set just last year)
* on track to break record for most 100+ degree days (12, already at 9)
There have been about 10 days so far I had to turn off some computers to reduce heat and 2 when I turned off all but my primary computer. I only remember about 4 last year when I had to turn off any computers.
____________
 |
|
|
|
|
|
So all this talk about heat - - You`d maybe think the PG staff has gotten
Hyperthermia and need rescue? ;-p Call the fire brigade. We need to get those challenge updates!
;-))
____________
|
|
|
|
|
|
Please You havr to wait...
http://www.primegrid.com/forum_thread.php?id=3462&nowrap=true#37675
Lennart |
|
|
|
|
Please You havr to wait...
http://www.primegrid.com/forum_thread.php?id=3462&nowrap=true#37675
Lennart
As I said earlier.... :P
____________
|
|
|
|
|
|
haha.. Thats exactly what we`re doing..  ...waiting..
____________
|
|
|
rroonnaallddVolunteer developer
Volunteer tester
Send message
Joined: 3 Jul 09
Posts: 1213
ID: 42893
Credit: 34,634,263
RAC: 0
|
|
Nice rabbit...
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
|
|
Nice rabbit...
Yup. Its what I see when I look in the mirror.. ;-p ;-)
____________
|
|
|
