No worries, I figured as much 
I see you’re implementing ghpythonlib.components for basically everything:
I really wouldn’t implement this node-in-code namespace unless you absolutely have to (i.e. some Grasshopper functionality isn’t part of RhinoCommon, or is from some plugin that doesn’t come with an API). There are several topics on problems associated with ghpythonlib.components that you might search for. I don’t recall if performance is one (it definitely was back in the day), but I’m sure there will be some overhead involved when writing code in such a roundabout way.
Instead, consider implementing RhinoCommon directly. Here’s a post on that topic and some additonal tips to speed up your GHPythoning: