Article View: gnu.chess
Article #2067Re: CPUs at 30 Ghz in the year 2005
From: Russell
Date: Sat, 19 May 2001 20:59
Date: Sat, 19 May 2001 20:59
50 lines
4208 bytes
4208 bytes
> > But what about parallel processing? If you are examining 1e9 positions a > > second, your numbers dwindle real quickly. > > > How long will it take you to search 10^50 positions at 10^9 positions > per second? > > hint: 10^41 seconds. _big_ number. It has been my experience that trying to explain that it's simply not possible for a chess program to search every possible sequence of moves is a frustrating, and most of the time, futile task to get the person to understand. The poster who said something about how 10^48 _appears_ "close" to 10^50 said it best. 10^48 is not anywhere close to 10^50. Here is a rough estimate: 10^50 - 10^48 = 9.9^49. Once you have searched 10^48 positions (which isn't going to happen), you still have another 9.9^49 to go (roughly). With each new level of the depth of the search you are going to multiply the time it took to do the previous search by the branching factor. With a branching factor of 35-38 (average number of chess moves in a given position), that means that once you've searched 10^15 positions, it's going to take you 35 to 38 times longer to search all of the positions from 10^15 up to 10^16. Even if you could reach 10^15 positions in your lifetime, 10^16 isn't likely to happen, and 10^17 is sure not to occur, now think about 10^50!! Now do you see why it's simply not possible? Here's a real life example: Let's say it takes you 1 year to search 10^15 positions in 1 second (which is nowhere close to a good estimate, I'm just using 1 second to make a point). If it took you 1 second to search 10^15 positions, it will take 35 seconds to search 10^16 positions. You can continue to multiply the time by 35 to get an estimate of how long it will take to search the next exponent power. Here are the numbers: 20 minutes to search 10^17 positions 12 hours to search 10^18 positions 17 days to search 10^19 positions 1.6 years to search 10^20 positions 58 years to search 10^21 positions 2,040 years to search 10^22 positions 71,406 years to search 10^23 positions 2,499,227 years to search 10^24 positions 87,472,962 years to serach 10^25 positions and so on... AND that is assuming that you can calculate 10^15 positions in 1 second, which you can not do, or even come close to doing.
Technical Details
Message-ID:
<9e6mqg$dop$1@oprah.cc.utexas.edu>Path:
arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.cs.utexas.edu!geraldo.cc.utexas.edu!not-for-mailReferences:
<PnWM6.120400$2_.38189249@news3.rdc1.on.home.com> <9e1g6o$4fs$1@oprah.cc.utexas.edu> <tg8s7fdkj8ln68@corp.supernews.com> <9e1vue$uil$1@juniper.cis.uab.edu> <LwmN6.16339$Az.1518318@newsread2.prod.itd.earthlink.net> <9e514d$vgq$1@juniper.cis.uab.edu> <3b066389.616017@news1.sympatico.ca> <q6scgtgi4n0a91us6sirq1tki5mco1gpvv@4ax.com> <j5yN6.19169$%i7.17308466@news1.rdc1.sfba.home.com> <9e6dnd$ga1$3@juniper.cis.uab.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1073e8,8df9b986ca792ae5 X-Google-Attributes: gid1073e8,public X-Google-Thread: f52e8,8df9b986ca792ae5 X-Google-Attributes: gidf52e8,public X-Google-Thread: 110df2,8df9b986ca792ae5 X-Google-Attributes: gid110df2,public X-Google-Thread: 10d71d,8df9b986ca792ae5 X-Google-Attributes: gid10d71d,public X-Google-Thread: 1035ff,8df9b986ca792ae5 X-Google-Attributes: gid1035ff,public X-Google-ArrivalTime: 2001-05-19 14:03:04 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.cs.utexas.edu!geraldo.cc.utexas.edu!not-for-mail From: "Russell" <rreagan@mail.utexas.edu> Newsgroups: gnu.chess,rec.games.chess.analysis,rec.games.chess.computer,rec.games.chess.misc,rec.games.chess.politics Subject: Re: CPUs at 30 Ghz in the year 2005 Date: Sat, 19 May 2001 15:59:59 -0500 Organization: The University of Texas at Austin; Austin, Texas Lines: 52 Sender: KGX08824@c1459884-c.cirving1.tx.home.com Message-ID: <9e6mqg$dop$1@oprah.cc.utexas.edu> References: <PnWM6.120400$2_.38189249@news3.rdc1.on.home.com> <9e1g6o$4fs$1@oprah.cc.utexas.edu> <tg8s7fdkj8ln68@corp.supernews.com> <9e1vue$uil$1@juniper.cis.uab.edu> <LwmN6.16339$Az.1518318@newsread2.prod.itd.earthlink.net> <9e514d$vgq$1@juniper.cis.uab.edu> <3b066389.616017@news1.sympatico.ca> <q6scgtgi4n0a91us6sirq1tki5mco1gpvv@4ax.com> <j5yN6.19169$%i7.17308466@news1.rdc1.sfba.home.com> <9e6dnd$ga1$3@juniper.cis.uab.edu> NNTP-Posting-Host: c1459884-c.cirving1.tx.home.com X-Trace: oprah.cc.utexas.edu 990305936 14105 65.3.49.176 (19 May 2001 20:58:56 GMT) X-Complaints-To: abuse@cc.utexas.edu NNTP-Posting-Date: 19 May 2001 20:58:56 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200