Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
1)
Message boards :
Number crunching :
Winter Solstice Challenge
(Message 123442)
Posted 1636 days ago by  nenym
This is the largest challenge we've ever done. The candidates being tested are 11 million digits in length. Even an SoB challenge at the leading edge would be only 9 million digits, and every GFN challenge we've run in the past included smaller GFN tasks. I am not sure. As I can remember, we have run GFN 22 during the 2014's Stallion Edition 15 days challenge.
|
2)
Message boards :
Number crunching :
Year of the Dog Challenge
(Message 116478)
Posted 1897 days ago by nenym
I believe this is the same Sebastien who runs WUProp, and if so, it's possible he may have abandoned both websites. I hope that's not true..... Sebastien who runs WUProp is active http://wuprop.boinc-af.org/forum_thread.php?id=351&postid=6065#6065
|
3)
Message boards :
Number crunching :
Happy New Year Challenge
(Message 113498)
Posted 1966 days ago by nenym
Just some questions about the app config Try to test your CPU by Prime95 http://www.mersenneforum.org/showthread.php?t=22377
|
4)
Message boards :
Number crunching :
Makar Sankranti Challenge
(Message 91028)
Posted 2705 days ago by nenym
my non-AVX machines:
Intel C2D E6550 @ 2.33GHz: GFN19 SSE2 transformation 34 hours (2 tasks concurrently)
AMD Phenom II X6 1090T: GFN19 SSE2 transformation 46 hours (6 tasks concurrently)
AMD RM-70: GFN17mega 80bit x87 transormation 67 hours (2 tasks concurrently) - ancient machine only for fun
|
5)
Message boards :
Number crunching :
Makar Sankranti Challenge
(Message 90993)
Posted 2706 days ago by nenym
We're off!
And this is strange. I'm running 3 WUs, all "18"s, on one machine:
This one's done about .5%.
This one's done about .5%.
This one's done about 2.7%!
Any idea why that one is so much faster? Have a look at stderr.txt in slots. Maybe slower tasks switched to more accurate transformations.
Example http://www.primegrid.com/result.php?resultid=677287611. Don't be surprised by times, it is ancient machine.
IMHO running GFN19 is better idea.
|
6)
Message boards :
The Riesel Problem :
Reducing TRP-Sieve deadline to 3 days, or increase everything to 4 days?
(Message 83734)
Posted 3016 days ago by nenym
My point of view:
24/7 machines: if a buffer set according to the CPU power, no problem for both DLs.
9/5 business/office desktop machines: 4 days DL means serious problem (buffer must be set under 0.9), 3 days DL means unusable application (or buffer < 0.1)
|
7)
Message boards :
Number crunching :
Year of the Sheep Challenge
(Message 82291)
Posted 3070 days ago by nenym
SoB: If you switched off the HT on i7-4960X your position would rise not slightly, but strongly.
It may be too late for that now, with less than 2 days to go.
Yes....I ought to write If you have had switched at the beginning...
|
8)
Message boards :
Number crunching :
Year of the Sheep Challenge
(Message 82289)
Posted 3070 days ago by nenym
SoB: If you switched off the HT on i7-4960X your position would rise not slightly, but strongly.
|
9)
Message boards :
Generalized Fermat Prime Search :
Vastly improved: AVX CPU Genefer Time
(Message 82203)
Posted 3072 days ago by nenym
At first: anonymous platform is not easy discipline.
- it is highly recommended to finish/abort all tasks of the project before changing to anonymous platform,
- any mistake in the app_info.xml means loss of tasks,
- it is able to crunch only apps, defined in app_info,
- it is necessary to download new versions of apps manually and maintain the structure and the content of <app_version> and <file_info> according to the actual version of apps,
- changing content of app_info.xml is high risk if any task is unfinished: you "must" prepare content of app_info according to the next PG challenge and duration of GFN WR task,
- turn back from anonymous platform to standard style (delete/rename of app_info.xml + restart Boinc core) means loss of all unreported tasks (=all tasks of the project "in BM') without any information about that issue to the server side, tasks are "abandoned".
Well, now the "GFN WR"part of app_info.xml for windows
<app_info>
<app>
<name>genefer_wr</name>
<user_friendly_name>Genefer WR</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
<name>primegrid_genefer_3_2_5_0_3.05_windows_x86_64__cpuGFN.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>genefer_wr</app_name>
<version_num>305</version_num>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<file_ref>
<file_name>primegrid_genefer_3_2_5_0_3.05_windows_x86_64__cpuGFN.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
Michael Goetz wrote: Such a change would likely benefit only a small number of people like yourself. The cost would be longer turn arounds for abandoned tasks. This doesn't sound like a good trade, in my opinion. I agree with you, let it be.If you miss the deadline by a few days, you'll always get credit. You don't have to be the second task; as long as you get the result in before the workunit is purged out of the database, you get credit. Nice, I had no knowledge of that difference to a standard credit system. Is it used for GFN/GFN WR tasks only or for all PG apps?
|
10)
Message boards :
Generalized Fermat Prime Search :
Vastly improved: AVX CPU Genefer Time
(Message 82187)
Posted 3072 days ago by nenym
Should be the DL of GFN WR tasks set to 27 - 32 days?
I'v tried to crunch a single GFN WR task by the cpuGFN app (Haswell i5-4570S, 3.1 GHz, RAM DDR3 1.6 GHz). The task was credited despite of the CPU time close to 24 days because of being the second successful result (Run time 2,050,188.91/ CPU time 1,977,637.00/credit 618,991.83).
By my point of view (and calculation of a power consumption) is more effective to crunch GFN WR tasks by cpuGFN app than by GPU app. I don't suppose that it is a good idea to enable the CPU crunching of GFN WR tasks to wide Boinc world, on the other side using anonymous platform could be a good idea - creators and users of app_info.xml are familiar with applications, tasks and bounds of usage. DL 27 -32 days could be acceptable for both GPU and anonymous platform CPU crunchers.
|
Next 10 posts
|
