![]() Week 13: Series summation is still past 47% complete. Makes us wonder why we were still running this. Week 12: Series summation is past 47% complete.įor a moment I pause to grasp what has happenned in Japan.Īnd the relief to have felt when I finally got that email from Shigeru Kondo Week 11: Series summation is still past 36% complete.Ĭheckpoint 3 Reached: Manual backup at 47%. Week 10: Series summation is still past 36% complete. Week 9: Series summation is past 36% complete. Hard Drive Write Error: Roll back to Checkpoint 4.Īll hard drives of the same model as the failed drive are replaced. Hard Drive Read Error: Roll back to Checkpoint 4. Week 8: Series summation is still past 36% complete.Ī backup was scheduled for when the 36% - 47% block was completed.īut a hard drive failed just before we got there. Week 7: Series summation is past 36% complete. Week 6: Series summation is still past 28% complete. Week 5: Series summation is past 28% complete. Week 4: Series summation is past 22% complete. Week 3: Series summation is past 17% complete. Week 2: Series summation is past 13% complete. Week 1: Series summation is past 6% complete. after I finish my midterms.ĭetailed Timeline (With Screenshots) Date See here for details.ġ0 Trillion Digits - Difficulties of this computation Nothing has really changed from last time. Yee) and are available for download from their respective pages. It's sole purpose was to verify the main computation.īoth programs are written by me (Alexander J. This program implements the digit-extraction algorithm for Pi using the BBP formulas. ![]() This is the exact same binary that we used to verify our previous computation. The program that was used for the verification is y-cruncher BBP v1.0.119. However, it was never completed in time for this computation. Originally, our plan was to use v0.6.1 which is expected to be a significantly faster than v0.5.5. Version v0.5.5 is virtually identical to v0.5.4 as it consists only of a few bug fixes and adds a few improvements that are irrelevant to this computation. See main page: y-cruncher - A Multi-Threaded Pi Program Multiple builds were used between the different times that the computation was interrupted. The program that was used for the main computation is y-cruncher v0.5.5. Software: y-cruncher - A Multi-Threaded Pi Program/BenchmarkĪs with the hardware, the software side hasn't had any changes since our previous computation. Processor 2 x Intel Xeon X5680 3.33 GHz - (12 physical cores, 24 hyperthreaded) Memory 96 GB DDR3 1066 MHz - (12 x 8 GB - 6 channels) Motherboard Asus Z8PE-D12 Hard Drives 1 TB SATA II (Boot drive)Ģ4 x 2 TB SATA II (Computation) - various models Raid Controller 3 x LSI MegaRaid SAS 9260-8i Operating System Windows Server 2008 R2 Enterprise 圆4 Built By Shigeru Kondo Pictures Click to enlarge. The only main difference is that there are more hard drives. The machine we used is mostly the same as the previous computation. To see how far can that limit of personal computing be pushed.Īs we will show, reaching 10 trillion digits of Pi is much more difficult than 5 trillion digits using our current methods and 2010 computer hardware. So the motivation and purpose is the same. This computation was basically a followup to our computation to 5 trillion digits. Note that the multicore efficiency % is inaccurate due to the numerous times that the computation has been interrupted.įor a detailed timeline of events related to this computation, see here. *All units used in this article are binary: If the digits were stored in an uncompressed ascii text file, the combined size of the decimal and hexadecimal digits would be 16.6 TB. Another 7.6 TB of disk was needed to store the compressed output of decimal and hexadecimal digits.Roughly 44 TB* of disk was needed to perform the computation.The result was approximately 180 days of lost time.ĭue to the size of this computation, a tremendous amount of memory was needed: Each of which required us to roll the computation back to a previous checkpoint. Over the course of the computation, there were multiple hard drive failures. The computer was dedicated for this task. The main computation took 371 days on Shigeru Kondo's desktop. However, due to the numerous times that the computation had been interrupted, the screenshot only shows the final leg of the computation as opposed to start -> finish. ![]() Just like last time, the full computation statistics are listed below. Computation Statistics - All times are Japan Standard Time (JST). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |