You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The draw module has not gotten much attention lately, but just wanted to note this here for those interested in potentially updating it in the future (and/or modifying the existing docs to point out alternatives!).
One change that can lead to a substantial improvement with relatively small changes to existing routines that grow Python lists of coordinates is refactoring the Cython code to use std::vector<Py_ssize_t> instead. I tried this locally just on the existing draw.polygon function and it does help, but I still don't think it is going to be competitive with the PIL implementation.
The text was updated successfully, but these errors were encountered:
There was also a function to draw a polyong into a pre-existing array proposed in #5453 that was faster than our existing routines, but also not competitive with PIL.
Description
@c-arthurs measured much poorer performance of polygon drawing in scikit-image as compared to PIL
The
draw
module has not gotten much attention lately, but just wanted to note this here for those interested in potentially updating it in the future (and/or modifying the existing docs to point out alternatives!).One change that can lead to a substantial improvement with relatively small changes to existing routines that grow Python lists of coordinates is refactoring the Cython code to use
std::vector<Py_ssize_t>
instead. I tried this locally just on the existingdraw.polygon
function and it does help, but I still don't think it is going to be competitive with the PIL implementation.The text was updated successfully, but these errors were encountered: