# Faster split in Python

**URL:** <https://discourse.mcneel.com/t/faster-split-in-python/23156>\
**Category:** Grasshopper\
**Created:** [August 3, 2015, 10:29pm UTC](https://discourse.mcneel.com/t/faster-split-in-python/23156 "2015-08-03T22:29:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lawrenceyy](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/lawrenceyy/32/353499_2.png) [@lawrenceyy](https://discourse.mcneel.com/u/lawrenceyy)\
**Post date:** [August 3, 2015, 10:29pm UTC](https://discourse.mcneel.com/t/faster-split-in-python/23156/1 "2015-08-03T22:29:46Z")

</div>

I’ve been using grasshopper for a while and it seems that the split component takes a lot longer to execute than the _split_ command in Rhino. I’ve tried doing _Rhino.Geometry.BrepFace.Split()_ via GhPython but that takes a long time too. Is there an alternative to split with curves that I am not seeing? I can literally split something in Rhino in less than a second, but then doing the same with _SrfSplit_ or via Rhinocommon takes 10x longer.

I posted this question to [grasshopper3d.com](http://grasshopper3d.com), but maybe you guys will be able to help: [http://www.grasshopper3d.com/forum/topics/faster-split](http://www.grasshopper3d.com/forum/topics/faster-split)

[split script.gh](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/8/8/8899e104e5e3530d00f61b255fcc4f61e0dc0261.gh) (7.8 KB) [split model.3dm](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/1/a/1ae2ce3bded95de9581a5bb06f474a31b88543ac.3dm) (42.6 KB)

Thanks

Lawrence Yun

---

<div class="post-metadata">

**Author:** ![stevebaer](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/stevebaer/32/473567_2.png) [@stevebaer](https://discourse.mcneel.com/u/stevebaer)\
**Post date:** [August 3, 2015, 10:34pm UTC](https://discourse.mcneel.com/t/faster-split-in-python/23156/2 "2015-08-03T22:34:48Z")

</div>

Hi Lawrence,  
@piac recorded this issue for us to investigate at  
[http://mcneel.myjetbrains.com/youtrack/issue/RH-31080](http://mcneel.myjetbrains.com/youtrack/issue/RH-31080)

---

<div class="post-metadata">

**Author:** ![lawrenceyy](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/lawrenceyy/32/353499_2.png) [@lawrenceyy](https://discourse.mcneel.com/u/lawrenceyy)\
**Post date:** [August 3, 2015, 10:44pm UTC](https://discourse.mcneel.com/t/faster-split-in-python/23156/3 "2015-08-03T22:44:18Z")

</div>

Well that’s good. I’m quite shocked that no one has ever thought to report this (I’ve suffered with _SrfSplit_ being slow for so many years now). I feel like there are a lot of grasshopper generated designs that rely on perforation (but I guess a lot of it is related to meshes and weaverbird). You would think this kind of inefficiency would have been corrected by now. I am going to more actively report issues from now on.

How will the fix be applied, will it be in the next grasshopper update?

Thanks.

---

<div class="post-metadata">

**Author:** ![stevebaer](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/stevebaer/32/473567_2.png) [@stevebaer](https://discourse.mcneel.com/u/stevebaer)\
**Post date:** [August 3, 2015, 11:20pm UTC](https://discourse.mcneel.com/t/faster-split-in-python/23156/4 "2015-08-03T23:20:15Z")

</div>

> [@lawrenceyy](#):
>
> How will the fix be applied, will it be in the next grasshopper update?

Changes like this require changes to core Rhino. We think we found a fix for this and will include it in the next V6 WIP. If you are willing to try the V6 WIP, I will set up your account so you have access to the application.