Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!news.nosignal.org!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.006 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'anyway.': 0.04; 'subject:Python': 0.05; 'case.': 0.05; 'deny': 0.07; 'subject:Windows': 0.09; 'compiler.': 0.09; 'statistical': 0.09; '3.3.': 0.16; 'accident.': 0.16; 'binaries': 0.16; 'build.': 0.16; 'guess.': 0.16; 'input.': 0.16; 'reliably': 0.16; 'subject:2.7.3': 0.16; 'whatsoever': 0.16; 'duplicate': 0.17; 'thorough': 0.17; 'tests': 0.18; 'to:name:python-list@python.org': 0.20; 'seems': 0.23; 'machine': 0.24; 'testing': 0.24; 'header:In-Reply-To:1': 0.25; 'regular': 0.27; 'run': 0.28; 'builds.': 0.29; 'cpu': 0.29; "i'm": 0.29; 'not.': 0.32; 'running': 0.32; 'builds': 0.33; 'turns': 0.33; 'to:addr:python-list': 0.33; 'thanks': 0.34; 'acceptable': 0.35; 'subject:?': 0.35; 'something': 0.35; 'there': 0.35; 'except': 0.36; 'tool': 0.36; 'but': 0.36; 'received:71': 0.36; 'useful': 0.36; 'charset:us-ascii': 0.36; 'problems': 0.36; 'itself': 0.37; 'subject:: ': 0.38; 'received:10': 0.38; 'sure': 0.38; 'performance': 0.39; 'to:addr:python.org': 0.39; 'build': 0.39; 'think': 0.40; 'days': 0.60; 'within': 0.64; 'confirm': 0.64; 'subject:Build': 0.65; 'subject:skip:D 10': 0.65; 'absolutely': 0.84; 'agenda.': 0.84; 'benchmark': 0.84; 'precompiled': 0.84; '30%': 0.93 From: "Leonard, Arah" To: "python-list@python.org" Subject: RE: Thorough Python 2.7.3 Windows Build Documentation? Thread-Topic: Thorough Python 2.7.3 Windows Build Documentation? Thread-Index: Ac30x2mWDSQparWUR2mEPGHjEuQjhQAOFtAAAAu2C4A= Date: Thu, 17 Jan 2013 17:09:42 +0000 References: <2ECADBDABCB17E40B66A25D839706F5E07585302@msnmail2.bruker-axs.com> <20130117161242.GA8527@sleipnir.bytereef.org> In-Reply-To: <20130117161242.GA8527@sleipnir.bytereef.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.73.1.96] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 17 Jan 2013 17:09:42.0546 (UTC) FILETIME=[710C5F20:01CDF4D5] X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 23 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1358442584 news.xs4all.nl 6950 [2001:888:2000:d::a6]:60604 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:36954 > I think the official binaries use the PGO build. Be sure to run all tests= thoroughly, we've had problems in with the PGO build in 3.3. Thanks Stefan. I hope that's not the case. PGO seems something of an an= athema from well-documented builds. Unless I'm missing something, if PGO i= s used it means that without knowing the specific CPU of the build machine = there would be no way to reliably duplicate the build except by accident. = Even with knowing, unless you have the same CPU... But after benchmarking a PGO build made by running the build_pgo.bat it tu= rns out that it made no difference whatsoever to my performance loss. With= in an acceptable statistical variation in the benchmark tool itself my PGO = build performed identically to my regular build. Which means that I'm stil= l running 30% slower than the precompiled binaries somehow even though I'm = theoretically using the right compiler. And which also means that I can ne= ither confirm nor deny if the released precompiled binaries are PGO builds = or not. It's one of those days I guess. But thanks anyway. I appreciate the usef= ul input. And yes, absolutely thorough testing is on the agenda. :) Sincerely, Arah Leonard