MMM
Results 1 to 25 of 815

Thread: New Multi-Threaded Pi Program - Faster than SuperPi and PiFast

Hybrid View

  1. #1
    Xtreme X.I.P. Particle's Avatar
    Join Date
    Apr 2008
    Location
    Kansas
    Posts
    3,219
    Timer sanity check failure.

    Code:
    Validation Version:  1.0
    
    Processor(s):        Six-Core AMD Opteron(tm) Processor 2427
    Logical Cores:       12
    Physical Memory:     8,587,915,264 ( 8.00 GB )
    CPU Frequency:       2,385,183,943
    
    Program Version:     0.5.2 Build 9082 Alpha 3 (x64 SSE3 - Windows ~ Kasumi)
    Constant:            Pi
    Algorithm:           Chudnovsky Formula
    Decimal Digits:      50,000,000
    Hexdecimal Digits:   Disabled
    Threading Mode:      16 threads
    Computation Mode:    Ram Only
    Swap Disks:          0
    Working Memory:      332 MB
    
    Start Time:          Sat Mar 20 01:19:53 2010
    End Time:            Sat Mar 20 01:20:16 2010
    
    Computation Time:    19.994 seconds
    Total Time:          21.454 seconds
    
    CPU Utilization:         825.39 %
    Multi-core Efficiency:   68.78 %
    
    Last Digits:
    4127897300 0153683630 8346732220 0943329365 1632962502  :  49,999,950
    5130045796 0464561703 2424263071 4554183801 7945652654  :  50,000,000
    
    Timer Sanity Check:      Failed
    Frequency Sanity Check:  Passed
    ECC Recovered Errors:    0
    
    ----
    
    Checksum:    53cc1527bc87df760d3dd7a2bb049be5848e39eb4325ca2c19572a8d6af91b1d
    Particle's First Rule of Online Technical Discussion:
    As a thread about any computer related subject has its length approach infinity, the likelihood and inevitability of a poorly constructed AMD vs. Intel fight also exponentially increases.

    Rule 1A:
    Likewise, the frequency of a car pseudoanalogy to explain a technical concept increases with thread length. This will make many people chuckle, as computer people are rarely knowledgeable about vehicular mechanics.

    Rule 2:
    When confronted with a post that is contrary to what a poster likes, believes, or most often wants to be correct, the poster will pick out only minor details that are largely irrelevant in an attempt to shut out the conflicting idea. The core of the post will be left alone since it isn't easy to contradict what the person is actually saying.

    Rule 2A:
    When a poster cannot properly refute a post they do not like (as described above), the poster will most likely invent fictitious counter-points and/or begin to attack the other's credibility in feeble ways that are dramatic but irrelevant. Do not underestimate this tactic, as in the online world this will sway many observers. Do not forget: Correctness is decided only by what is said last, the most loudly, or with greatest repetition.

    Rule 3:
    When it comes to computer news, 70% of Internet rumors are outright fabricated, 20% are inaccurate enough to simply be discarded, and about 10% are based in reality. Grains of salt--become familiar with them.

    Remember: When debating online, everyone else is ALWAYS wrong if they do not agree with you!

    Random Tip o' the Whatever
    You just can't win. If your product offers feature A instead of B, people will moan how A is stupid and it didn't offer B. If your product offers B instead of A, they'll likewise complain and rant about how anyone's retarded cousin could figure out A is what the market wants.

  2. #2
    Xtreme Enthusiast
    Join Date
    Mar 2009
    Location
    Bay Area, California
    Posts
    705
    Quote Originally Posted by Particle View Post
    Timer sanity check failure.

    Code:
    Validation Version:  1.0
    
    Processor(s):        Six-Core AMD Opteron(tm) Processor 2427
    Logical Cores:       12
    Physical Memory:     8,587,915,264 ( 8.00 GB )
    CPU Frequency:       2,385,183,943
    
    Program Version:     0.5.2 Build 9082 Alpha 3 (x64 SSE3 - Windows ~ Kasumi)
    Constant:            Pi
    Algorithm:           Chudnovsky Formula
    Decimal Digits:      50,000,000
    Hexdecimal Digits:   Disabled
    Threading Mode:      16 threads
    Computation Mode:    Ram Only
    Swap Disks:          0
    Working Memory:      332 MB
    
    Start Time:          Sat Mar 20 01:19:53 2010
    End Time:            Sat Mar 20 01:20:16 2010
    
    Computation Time:    19.994 seconds
    Total Time:          21.454 seconds
    
    CPU Utilization:         825.39 %
    Multi-core Efficiency:   68.78 %
    
    Last Digits:
    4127897300 0153683630 8346732220 0943329365 1632962502  :  49,999,950
    5130045796 0464561703 2424263071 4554183801 7945652654  :  50,000,000
    
    Timer Sanity Check:      Failed
    Frequency Sanity Check:  Passed
    ECC Recovered Errors:    0
    
    ----
    
    Checksum:    53cc1527bc87df760d3dd7a2bb049be5848e39eb4325ca2c19572a8d6af91b1d
    That's interesting... I guess I overestimated the precision of the hardware timers on some of these motherboards...

    Another thing to add to my to-do list for v0.5.3.

    Anyways, I'm off for the night. Gotta catch a plane tomorrow morning.
    Last edited by poke349; 03-19-2010 at 10:40 PM.
    Main Machine:
    AMD FX8350 @ stock --- 16 GB DDR3 @ 1333 MHz --- Asus M5A99FX Pro R2.0 --- 2.0 TB Seagate

    Miscellaneous Workstations for Code-Testing:
    Intel Core i7 4770K @ 4.0 GHz --- 32 GB DDR3 @ 1866 MHz --- Asus Z87-Plus --- 1.5 TB (boot) --- 4 x 1 TB + 4 x 2 TB (swap)

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •