Databases
StackOverflow2013
Postsdbo
POCythonized function unexpectedly slow
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCythonized function unexpectedly slow
    primarykey
    data
    text
    <p>I wanted to speed up a function that I'm using a lot and I though about using cython. However, after trying all the possible cython optimizations that I've been able to find in the documentation, the cython code is about 6 times slower than the python+numpy function. Disappointing! </p> <p>This is my test code: (forward1 is the python function, forward2 is the cython function)</p> <pre><code>#geometry.py def forward1(points, rotation, translation): '''points are in columns''' return np.dot(rotation, points - translation[:, np.newaxis]) #geometry.pyx import numpy as np cimport numpy as np cimport cython @cython.boundscheck(False) @cython.wraparound(False) @cython.nonecheck(False) cdef np.float64_t[:,:] forward2(np.float64_t[:,:] points, np.float64_t[:,:] rotation, np.float64_t[:] translation): '''points are in columns''' cdef unsigned int I, J I = points.shape[0] J = points.shape[1] cdef np.float64_t[:,:] tmp = np.empty((I, J), dtype=np.float64) cdef unsigned int i for i in range(J): tmp[0, i] = points[0, i] - translation[0] tmp[1, i] = points[1, i] - translation[1] cdef np.float64_t[:,:] result = np.dot(rotation, tmp) return result def test_forward2(points, rotation, translation): import timeit cdef np.float64_t[:,:] points2 = points cdef np.float64_t[:,:] rotation2 = rotation cdef np.float64_t[:] translation2 = translation t = timeit.Timer(lambda: forward2(points2, rotation2, translation2)) print min(t.repeat(3, 10)) </code></pre> <p>and then I time it:</p> <pre><code>t = timeit.Timer(lambda: forward1(points, rotation, translation)) print min(t.repeat(3, 10)) 0.000368164520751 test_forward2(points, rotation, translation) 0.0023365181969 </code></pre> <p>Is there anything I can do to the cython code to make it faster?</p> <p>If forward1 can't be sped up in cython, can I hope any speed up using weave? </p> <p><strong>EDIT:</strong></p> <p>Just for the record, another thing I've tried to speed up the function is to pass points in fortran order, as my points are stored in columns and there are quite a few of them. I also define the local tmp as fortran order. I think the subtraction part of the function should be faster but numpy.dot seems to require a C order output (anyway to work around this?), so altogether there is no speed up with this either. I also tried to transpose the points so that the subtraction part is faster in C order, but it seems the dot product is still the most expensive part.</p> <p>Also, I noticed that numpy.dot can't use memoryviews as out argument, even if it's C order, is this a bug?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJoe Kington
    1. USmartinako
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCythonized function unexpectedly slow
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`numpy` is already using `c` and `fortran` libraries for calculations. usually you don't need to do anything to get speedups..
      singulars
      1. POCythonized function unexpectedly slow
      1. USnone
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload