# Ghpython - Parallel Component Slower than Native Ghopper Module

**URL:** <https://discourse.mcneel.com/t/ghpython-parallel-component-slower-than-native-ghopper-module/6360>\
**Category:** Grasshopper\
**Created:** [February 27, 2014, 8:57am UTC](https://discourse.mcneel.com/t/ghpython-parallel-component-slower-than-native-ghopper-module/6360 "2014-02-27T08:57:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![piac](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/piac/32/769366_2.png) [@piac](https://discourse.mcneel.com/u/piac)\
**Post date:** [March 25, 2014, 8:49am UTC](https://discourse.mcneel.com/t/ghpython-parallel-component-slower-than-native-ghopper-module/6360/6 "2014-03-25T08:49:24Z")

</div>

Hello everyone,

occasionally somebody posts this kind of results, and I’ve noticed that very often this has to do with speed-up structures that are used to make finding points faster.  
For example, Gwyll, [in this discussion](http://www.grasshopper3d.com/forum/topics/demonstrating-recursion-any-idea-why-ghpythonlib-runs-so-slowly), was experiencing exactly this.

I will have a look at this case now - and see if I discover something.  
Thanks,

## Giulio

Giulio Piacentino  
for Robert McNeel & Associates  
[giulio@mcneel.com](mailto:giulio@mcneel.com)

---

_[View the full topic](https://discourse.mcneel.com/t/ghpython-parallel-component-slower-than-native-ghopper-module/6360)._