Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Daniel Lord
Jack, My bus is 1.33 GHz--I think the 2nd Gen Quad-cores are bumped to 1.5 GHz maybe. I'll see if there is anything I can do to bump the numbers. My system is just like yours but with a second Quad core chip that only a few apps can take advantage of. It helps me with Modo, Lightwave, Shake, P

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Daniel Lord
Will do, though I am not expecting great results given what we know now. I'll post the numbers as soon as I can get it done. On Jan 20, 2008, at 11:05 PM, Ronald Oussoren wrote: > > On 20 Jan, 2008, at 19:23, Daniel Lord wrote: > >> I ran the test on my 1st Gen Quad Core ( 2 x Quad-core 3.0 GHz,

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Ronald Oussoren
On 20 Jan, 2008, at 19:23, Daniel Lord wrote: I ran the test on my 1st Gen Quad Core ( 2 x Quad-core 3.0 GHz, 13GB RAM) and was a bit surprised to see little improvement over the Core Duo numbers. 63019.7 pystones/second I am assuming the GIL is limiting threading and therefore I am really

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread skip
Jack> So: any other speculations as to why 2.66Ghz->3.0Ghz gives only a 1% Jack> increase in pystones? Maybe compilation flags. Skip ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Ian Baird
Hmm - that appears to be negligible if not within the bounds of statistical error. However, you're right - a small bump in speed. A Quick Aside: Benchmarking the diff routines on my app (Changes - http://changesapp.com/) showed a 10-15% performance increase going from 32-bit i386 to 64- bit

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Jack Jansen
On 20-Jan-2008, at 20:53 , [EMAIL PROTECTED] wrote: >Daniel> I am assuming the GIL is limiting threading and therefore > I am >Daniel> really running on one or two cores--hence the tangible >Daniel> improvement is just CPU speed: from 2.33 GHz to 3.0 GHz > and a >Daniel> bit o

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread skip
Ian> It would be interesting to see if that held up on ppc64. My guess Ian> is that it would benchmark slower in 64-bit mode than 32-bit mode Ian> on ppc. I added a pystone entry to the table for my G5 with the Python 2.6a0 interpreter compiled with -fast -fPIC -fwrapv. I saw a reaso

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Ian Baird
It would be interesting to see if that held up on ppc64. My guess is that it would benchmark slower in 64-bit mode than 32-bit mode on ppc. - Ian On Jan 20, 2008, at 2:27 AM, Ronald Oussoren wrote: > > On 19 Jan, 2008, at 21:43, [EMAIL PROTECTED] wrote: > >> >> My Powerbook G4 is getting rathe

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Jack Jansen
On 20-Jan-2008, at 19:23 , Daniel Lord wrote: > I ran the test on my 1st Gen Quad Core ( 2 x Quad-core 3.0 GHz, 13GB > RAM) and was a bit surprised to see little improvement over the Core > Duo numbers. > > 63019.7 pystones/second > > I am assuming the GIL is limiting threading and therefore I

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread skip
Daniel> I am assuming the GIL is limiting threading and therefore I am Daniel> really running on one or two cores--hence the tangible Daniel> improvement is just CPU speed: from 2.33 GHz to 3.0 GHz and a Daniel> bit of the memory bandwidth increase as well. The GIL doesn't enter in

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Daniel Lord
I ran the test on my 1st Gen Quad Core ( 2 x Quad-core 3.0 GHz, 13GB RAM) and was a bit surprised to see little improvement over the Core Duo numbers. 63019.7 pystones/second I am assuming the GIL is limiting threading and therefore I am really running on one or two cores--hence the tang

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Henning Hraban Ramm
Am 2008-01-19 um 21:43 schrieb [EMAIL PROTECTED]: > If you could help by adding some rows to the table, especially for > current > MacBook, MacBook Pro or (in the near future, MacBook Air) models, I'd > appreciate it. I guess it doesn't really matter, but my trusty old steam powered G4/400 on

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Ronald Oussoren
On 20 Jan, 2008, at 16:27, [EMAIL PROTECTED] wrote: Ronald> What is interesting though is the difference between 32- bit and Ronald> 64-bit code: Ronald> Python 2.5.2a0 (60124) Ronald> 32-bit: 52083 Ronald> 64-bit: 60871 Ronald> 64-bit code is significantly faster here (al

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread skip
Ronald> What is interesting though is the difference between 32-bit and Ronald> 64-bit code: Ronald> Python 2.5.2a0 (60124) Ronald> 32-bit: 52083 Ronald> 64-bit: 60871 Ronald> 64-bit code is significantly faster here (all of this on a Ronald> MacBook Pro 2.33Ghz/3GByt

Re: [Pythonmac-SIG] Re-beginner's simple question

2008-01-20 Thread Ronald Oussoren
On 20 Jan, 2008, at 9:26, Kenneth Miller wrote: Charles, That seems normal. Here's a bash script I use for compiling my application. I don't mess with the setup.py once it's generated, and this bash script seems to do the trick. rm -r build rm -r dist py2applet --make-setup Decod

Re: [Pythonmac-SIG] Pystone numbers for different Macs...

2008-01-20 Thread Ronald Oussoren
On 19 Jan, 2008, at 21:43, [EMAIL PROTECTED] wrote: My Powerbook G4 is getting rather long-in-the-tooth. It's display is starting to act up, so I think I'm going to buy a new Mac something in the fairly near future, but I'm not yet sure what. To that end, I've started a table of pystone

Re: [Pythonmac-SIG] Re-beginner's simple question

2008-01-20 Thread Kenneth Miller
Charles, That seems normal. Here's a bash script I use for compiling my application. I don't mess with the setup.py once it's generated, and this bash script seems to do the trick. rm -r build rm -r dist py2applet --make-setup Decoder.py python setup.py py2app --include DUtils,LabVI