Re: [GRASS-dev] Benchmark the overhead of calling GRASS modules

hello Markus and Vaclav, thank you for your feedback. My answer is inline. On Wed, May 1, 2019 at 6:03 PM Markus Metz wrote: > IMHO the overhead of calling GRASS modules is insignificant because it is > in the range of milliseconds. I am much more concerned whether executing a > GRASS module

Re: [GRASS-dev] Benchmark the overhead of calling GRASS modules

Hi Panos and Markus, I actually touched on this in my master's thesis [1, p. 54-58], specifically on the subprocess call overhead (i.e. not import or initialization overheads). I compared speed of calling subprocess in Python to a Python function call. The reason was that I was calling GRASS

Re: [GRASS-dev] Benchmark the overhead of calling GRASS modules

Hi Panos, IMHO the overhead of calling GRASS modules is insignificant because it is in the range of milliseconds. I am much more concerned whether executing a GRASS module takes days or hours or minutes. Also note that the base of GRASS are C modules using the GRASS C library. GRASS python

[GRASS-dev] Benchmark the overhead of calling GRASS modules

Hello all You might find it easier to read the following text i n a gist ## Introduction I was trying to write a decorator/contextmanager that would temporary