Re: [Pythonocc-users] pythonOCC perfomance

2011-10-09 Thread Stephen Waterbury
Istvan, In addition to Thomas's recommendation, you might also have a look at http://wiki.python.org/moin/PythonSpeed/PerformanceTips ... and more specifically: http://wiki.python.org/moin/PythonSpeed/PerformanceTips#Loops It is well-known among experienced Python programmers that for loops are

Re: [Pythonocc-users] pythonOCC perfomance

2011-10-09 Thread Thomas Paviot
Hi Istvan, It's not a surprise that the python code is slower than the equivalent C++ code. Have a look at the file src/wrapper/SWIG_files/linux_darwin/gp_wrap.cpp (the C++ file generated with swig): you can see that creating a gp_Pnt from coordinates requires that the _wrap_new_gp_Pnt function is

[Pythonocc-users] pythonOCC perfomance

2011-10-08 Thread István Csanády
Hi, I made some tests with pythonOCC and with the pure C++ OCE. According to my measurements the 'same' code in python is about 10 times slower than the C++ code. For example the following python code: for i in xrange(1): p = gp_Pnt(0,0,0) face = BRepBuilderAPI_MakeFace(gp_Sp