Kevin Jacobs <[EMAIL PROTECTED]> wrote: > On 7/19/06, *Travis Oliphant* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Kevin Jacobs <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > On 7/19/06, *Kevin Jacobs <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > <mailto: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>>>* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> > wrote: > > > > Is it expected that the following script would spend over > half of > > the total execution time in > defmatrix.py:103(__array_finalize__)? > > > > > > Confirmed that a similar overhead exists for arrays, though not as > > extreme. My application requires the ability to assign random > > elements, so any speed ups here will result be quite significant. > > > There is an optimization for this kind of assignment in current NumPy > SVN which "should" avoid the array creation over-head. > > > > There still seems to be a huge performance penalty with using a matrix > to set elements. Consider this code where X is initially a matrix:
Are you now using SVN NumPy, or are we still looking at NumPy 0.9.8 numbers? -Travis ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion
