Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #36956 > unrolled thread
| Started by | Stefan Krah <stefan@bytereef.org> |
|---|---|
| First post | 2013-01-17 18:29 +0100 |
| Last post | 2013-01-17 18:29 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Thorough Python 2.7.3 Windows Build Documentation? Stefan Krah <stefan@bytereef.org> - 2013-01-17 18:29 +0100
| From | Stefan Krah <stefan@bytereef.org> |
|---|---|
| Date | 2013-01-17 18:29 +0100 |
| Subject | Re: Thorough Python 2.7.3 Windows Build Documentation? |
| Message-ID | <mailman.599.1358443791.2939.python-list@python.org> |
Leonard, Arah <Arah.Leonard@bruker-axs.com> wrote: > But after benchmarking a PGO build made by running the build_pgo.bat it turns out that it made no difference whatsoever to my performance loss. Within an acceptable statistical variation in the benchmark tool itself my PGO build performed identically to my regular build. Which means that I'm still running 30% slower than the precompiled binaries somehow even though I'm theoretically using the right compiler. And which also means that I can neither confirm nor deny if the released precompiled binaries are PGO builds or not. I remember that some versions of Visual Studio silently completed the PGO build without actually having PGO capabilities. :) I think for VS 2008 at least "Professional" is needed, for VS 2010 "Ultimate". Stefan Krah
Back to top | Article view | comp.lang.python
csiph-web