The Third Megabit Drive
1 Attachment(s)
We are starting the Third Megabit Drive.
The k's on this current drive, as of 30 May 2014, are at level n=1.4M therefore the goal of this drive is to take them up to 2M. Goal can be prior extended. The k's of this drive are: 203, 205, 219, 227, 235, 257, 259 [B]Update (June 03, 2014):[/B] adding k=275 and k=295 to the drive from n=1680k. Range n=14001680k for both k added as "batch 2". [B]Update (June 08, 2014):[/B] batch 2 completed. [B]Update (July 09, 2014):[/B] The drive is completed to n=2M. [B] Update (June 16, 2015):[/B] Reopening the drive from n=2M. Please help yourself and happy hunting! :smile: [B]Status[/B] Batch 1 (7 k's to n=1680k and all 9 k's from n=1680k) [CODE] Range of n Tested by Status 1,400,0001,404,000  Carlos  Complete 1,404,0001,408,000  Trilo  Complete 1,408,0001,412,000  Thomas  Complete 1,412,0001,418,000  Carlos  Complete 1,418,0001,450,000  kracker  Complete 1,450,0001,720,000  Batalov  Complete (5 primes) 1,720,0001,728,000  Carlos  Complete 1,728,0001,740,000  kracker  Complete 1,740,0001,750,000  Carlos  Complete 1,750,0001,800,000  kracker  Complete 1,800,0001,820,000  Carlos  Complete 1,820,0001,834,000  Batalov  Complete (2 primes) 1,834,0001,838,000  Carlos  Complete 1,838,0001,854,000  Batalov  Complete (1 prime) 1,854,0001,866,000  Carlos  Complete 1,866,0002,000,000  Batalov  Complete 2,000,0002,003,175  Carlos  Complete 2,003,1762,025,000  Thomas11  Complete 2,025,0002,027,970  Carlos  Complete 2,027,9712,050,000  Thomas11  Complete 2,050,0002,050,963  Carlos  Complete 2,050,9632,060,000  Curtis  Complete 2,060,0002,102,000  Kosmaj  Complete 2,102,0002,200,000  gd_barnes  Complete (3 primes) [/CODE]Batch 2 (k=275 and 295 from n=1400k to n=1680k) [CODE] Range of n Tested by Status 1,400,0001,420,000  Carlos  Complete 1,420,0001,680,000  Batalov  Complete [/CODE][B]Test Files[/B] Extensively sieved by Psieve (the latest sieve file of July 31, 2011) See attachment with candidates from n=2M to 3M (split into 2k blocks, kindly prepared by Carlos). [B]FFT lengths[/B] Up to about n=1820k the 112k FFT will be used. AVX machines will benefit from the intermediate 120k FFT in the n=18501960k interval, where nonAVX machines will use the 128k FFT instead. PS (Please attach zipped results naming like TMD_1400to1405.txt.zip and so on) [B]Updated 20210504[/B] Found Primes: 203 [0]: 205 [2]: 1537779, 1666435 219 [1]: 2178673 227 [0]: 235 [3]: 1718787, 1824515, 2163273 257 [2]: 1658254, 2108554 259 [1]: 1695723 275 [1]: 1846390 295 [1]: 1832129 Total: 11 primes (Found primes for 7 out of 9 k's) . 
Hi Carlos
Thanks for starting the drive. I'm busy right now but will join the drive soon. Happy hunting! :smile: 
Taking 14001404.
Edit: Fast machines can test a candidate at n=1.4M in 500 seconds or less. Come on guys! 
Sorry for not splitting the input files into chunks but I don't know how to do it automatically. Also as the numbers are very fast to process, on latest Intel processors they can take less than 500 secs, I don't know what is the optimal chunk size for now for this drive, if 2k or 4k or 6k, for a period of 710 days of crunching as usual done on the other drives.
Carlos 
Taking 1404 to 1408

About automatically splitting the files
I may be able to help you out by automatically splitting the files if you want. Do you need them in splits of 1000 or 2000?

I splitted the 1.42M input file into 2k blocks (see attachment). Each block contains about 400 test candidates.
The attached ZIP file also contains a file called "url_list.txt" indicating the FFT lengths and percentages (for nonAVX machines). This file is only relevant for Kosmaj when uploading the files to his server... [I]Edit:[/I] Attachment removed. Please use the file in the top post of this thread... 
Taking 14081412.

Taking 14121418.

Taking 14181430.

Hmm... going though them faster than expected, 2k done. Taking 14301450. (separate reservation if possible please)

Yep, they run fast. My first reservation is 60 % complete and I think from now on until we reach next FFT jump I will start reserving a 10k block per core.
Carlos 
I'm running it at 2600 sec a candidate with 4 cores, my fast computer is working on the 8th drive. I'll have my range done in the next 6 days or so.

Taking 14501600.

[QUOTE=Batalov;374843]Taking 14301600.[/QUOTE]
kracker reserved from 14301450. 
Ok, then.
Now you know that it is a fulltime job to be a "manager" (or a "makesurerer", take your pick) of a drive. Please be fast and update the reservation post fast so that the users are not confused. You have been in the shoes of a user for too long. Now, learn to be an effective manager. ;) 
[QUOTE=Batalov;374845]Ok, then[/QUOTE]
Now you just need to update first post. kracker reservation was in the middle of a conversation and therefore probably unnoticeable. [QUOTE=Batalov;374845]Now you know that it is a fulltime job to be a "manager" (or a "makesurerer", take your pick) of a drive. Please be fast and update the reservation post fast so that the users are not confused. You have been in the shoes of a user for too long. Now, learn to be an effective manager. ;)[/QUOTE] It is not my fault...I am a simple cruncher not moderator. 
[QUOTE=pinhodecarlos;374846]I am a simple cruncher not moderator.[/QUOTE]
Talk about being confused. Why do you start a drive that you have no intention of managing, then? 
[QUOTE=Batalov;374847]Talk about being confused.
Why do you start a drive that you have no intention of managing, then?[/QUOTE] As many started here by others. Kosmaj gave me permission to start it. Also the current three moderators can handle the work although I think it misses one from side of America's (north and south of America). One is in the UK, other in Japan and the last one in Germany. 
14501600 is done.
Carrying on to 16001680. Results will be in one file. 
Thank you Batalov for the push.
Meanwhile here are the Nash Weight of the k's: k=203  NW=1687 k=205  NW=1351 k=219  NW=1069 k=227  NW=2550 k=235  NW=1241 k=257  NW=1867 k=259  NW=1561 Carlos EDIT: Damn, I didn't see the k=275 still in n=1.4M. It should be on this drive too. 
[QUOTE=pinhodecarlos;374933]Thank you Batalov for the push.
Meanwhile here are the Nash Weight of the k's: k=203  NW=1687 k=205  NW=1351 k=219  NW=1069 k=227  NW=2550 k=235  NW=1241 k=257  NW=1867 k=259  NW=1561 Carlos EDIT: Damn, I didn't see the k=275 still in n=1.4M. It should be on this drive too.[/QUOTE] I can run 275 from 1.4M to 1.6M then we can enter it into the drive past there. 
[QUOTE=Trilo;374936]I can run 275 from 1.4M to 1.6M then we can enter it into the drive past there.[/QUOTE]
The files slitted in 2k blocks were already prepared so I think it is better to run it alone until 2M. How many cores do you have? Do you have the file? 
I will have 4 cores available once my reservation on 14041408 is finished. I can get the files from primegrid's sieving files.

If you are not going to add it to the drive then I won't test it, but if you want to add it to the drive then I will test it.

Let's wait for Kosmaj or Thomas reply.

[QUOTE=pinhodecarlos;374941]Let's wait for Kosmaj or Thomas reply.[/QUOTE]
That's fine. 275 has a weight of 1581 so it won't take too long to test. 
[QUOTE=pinhodecarlos;374941]Let's wait for Kosmaj or Thomas reply.[/QUOTE]
I've added k=275 to the input files starting from n=1680k. The ZIP file in the first post of this thread has been replaced and now contains the whole file (rps_M3.txt, n=16802000k) as well as the split files (2k blocks). There is also the file for k=275 included (t17_b2_k275.npg, n=10002000k) for individual testing the n=14001680k range. 
Thomas, k=295 is also stopped at 1.4M. Let's add this one too?

[QUOTE=pinhodecarlos;374951]Thomas, k=295 is also stopped at 1.4M. Let's add this one too?[/QUOTE]
Okay, it's been added too. The ranges n=14001680k for both k (275 and 295) are open for individual testing. Please post your reservations and results to this thread. 
1 Attachment(s)
14501680 is done, 3 primes.

1 Attachment(s)
14021404 complete, no primes. (7 k's)

Taking 275 and 295 from 1400 to 1420.

1 Attachment(s)
14001402 complete, no primes. (7' k's)

Ok, I'll catch up the batch 2 from 1.42 to 1.68.
...and taking 1.681.72 (all k) 
1 Attachment(s)
14181430 no primes.

1 Attachment(s)
[QUOTE=Batalov;374995]Ok, I'll catch up the batch 2 from 1.42 to 1.68.
...and taking 1.681.72 (all k)[/QUOTE] Both done and attached. 2 primes. 
Now that the 2 extra k's have been all caught up, I think we should remove the "batch 2" part of the reservations to avoid confusion when Carlos is done with his range.

[QUOTE=Trilo;375073]Now that the 2 extra k's have been all caught up, I think we should remove the "batch 2" part of the reservations to avoid confusion.[/QUOTE]
Not yet, I am still doing a little part. More 4 days. 
[QUOTE=pinhodecarlos;375074]Not yet, I am still doing a little part. More 4 days.[/QUOTE]
Yeah just realized you were not done with your reservation and edited my post right as you said this :max: 
My reservation is 25 % complete. The server has 6 cores available that I could use but I don't know if I should. There's no queue work system, work is inserted manually.

1 Attachment(s)
14121414 complete, no primes. (7' k's)

Taking 17201728. (9 k's)

1 Attachment(s)
1430 to 1450, no primes.

1 Attachment(s)
14001420 complete, no primes. (2 k's  batch 2)
Maybe clean on first post in order?! 
I was wondering if it isn't better to switch the order of the status progress by putting the batch 2 information in first. Thoughts please?

taking 1728 to 1740

1 Attachment(s)
14141416 complete, no primes. (7 k's)

14041408 complete, no primes

[QUOTE=pinhodecarlos;375348]I was wondering if it isn't better to switch the order of the status progress by putting the batch 2 information in first. Thoughts please?[/QUOTE]
Now that batch 2 is complete, I say we remove it from the list entirely. 
[QUOTE=Trilo;375421]14041408 complete, no primes[/QUOTE]
Please attach the results. 
Taking 17401750.

1 Attachment(s)
14081412 complete, no primes.

1 Attachment(s)
1728to1740 no primes.

taking 1750 to 1800.

Taking 18001804.

1 Attachment(s)
14161418 complete, no primes (7 k's)

1 Attachment(s)
[QUOTE=pinhodecarlos;375431]Please attach the results.[/QUOTE]
I split it into a few separate files so I have attached them. 
Taking 18041806.

1 Attachment(s)
17201722 complete, no primes.

Taking 18061810.

Candidates left from 18102000: 46135.

Taking 18101814.

Taking 18141854.
All separate reservations. 
1 Attachment(s)
18041806 complete, no primes.

1 Attachment(s)
18001802 complete, no primes.

Taking 18541856.

1 Attachment(s)
18101812 complete, no primes.
Taking 18561858. 
1 Attachment(s)
17221728 complete, no primes.

1 Attachment(s)
18061808 complete, no primes.

1 Attachment(s)
18121814 complete, no primes.

Taking 18581860.

1 Attachment(s)
17401750 complete, no primes.

Taking 18601862.

1 Attachment(s)
18021804 complete, no primes.

1 Attachment(s)
18141816 complete, no primes.

1 Attachment(s)
[QUOTE=pinhodecarlos;376351]Taking 18541856.[/QUOTE]
Done. No primes. 
1 Attachment(s)
18561858 complete, no primes.

1 Attachment(s)
18081810 complete, no primes.
So 17401750 is done as well as 18001816. 
1 Attachment(s)
1750to1800 no primes.

Taking 18621864 and 18641866. (4 cores)

1 Attachment(s)
18581860 complete, no primes.

1 Attachment(s)
18601862 complete, no primes.
Means: [code] 1,800,0001,816,000  Carlos  Complete 1,816,0001,854,000  Carlos  In Progress 1,854,0001,856,000  Carlos  Complete 1,856,0001,862,000  Carlos  Complete 1,862,0001,864,000  Carlos  In Progress 1,864,0001,866,000  Carlos  In Progress [/code] 
1 Attachment(s)
18161818 complete, no primes.

Taking 1.8662M

1 Attachment(s)
[B]Update (July 04, 2014):[/B] extending drive to 3M.
241689 candidates in the attachment extensively sieved by Psieve (the latest sieve file of July 31, 2011) 
Batalov,
My range 18181854 is in progress like this: 18181820 in progress 18201834 in queue 18341838 complete 18381854 in queue. 18621866 almost complete. Do you want to crunch the ranges in queue? If so please let me know so I can add work from Second Megabit Drive, where I want to concentrate from now on my efforts. Carlos 
No, let's keep it simple, as is.

[QUOTE=Batalov;377412]No, let's keep it simple, as is.[/QUOTE]
Thank you and happy crunching! My ranges below 1854 will take at least one month, I am now down to 2 cores at home and so far 10 at work. 18621866 will be done within max 2 days, so of the 10 cores more 4 will be down soon, leaving 6 to finish my current SMD reservations. By Monday all 10 cores will complete their jobs. 
Hi Carlsos,
Please consider releasing your second queue (18381854), thus speeding up the processing of the first one and giving a chance to others to complete the range of the second queue and the whole Drive to 2M faster. Thanks. 
[QUOTE=Kosmaj;377419]Hi Carlsos,
Please consider releasing your second queue (18381854), thus speeding up the processing of the first one and giving a chance to others to complete the range of the second queue and the whole Drive to 2M faster. Thanks.[/QUOTE] I prefer to release both queues. So the board will be look like this [code] 1,750,0001,800,000  kracker  Complete 1,800,0001,818,000  Carlos  Complete 1,818,0001,820,000  Carlos  In progress [B]1,820,0001,834,000  Available  Free[/B] 1,834,0001,838,000  Carlos  In progress [B]1,838,0001,854,000  Available  Free[/B] 1,854,0001,862,000  Carlos  Complete 1,862,0001,864,000  Carlos  In Progress 1,864,0001,866,000  Carlos  In Progress 1,866,0002,000,000  Batalov  In Progress [/code]I need an answer, almost midnight here, I want to sleep but before I go I need to reserve a SMD range to one of the cores. 
Releasing the ranges in bold from previous post. I think it will be quicker if done by others rather by only two of my laptop cores. Tomorrow I will publish 18341838 results.
Going now to bed. Bye. Carlos 
Thanks!
I just uploaded remaining test files to my server, and added links to them in the first post of the thread. 
1 Attachment(s)
18341838 complete, no primes.

1 Attachment(s)
18621864 complete, no primes.

I am going to dedicate one core here one core on SMD.
I ask for some help to help to clean the drive up to 2M. On my laptop each candidate is tested in less than 1200 secs so I suppose with processors with AVX 2.0 it will crunch in less than 900 secs. Within 2 days I will reserve another 2k chunk. Meanwhile 18641865 is complete, waiting for 18651866 (5 candidates left), and another core down for me. Carlos 
1 Attachment(s)
18641866 complete, no primes.

All times are UTC. The time now is 06:01. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2022, Jelsoft Enterprises Ltd.