Grasshopper

algorithmic modeling for Rhino

Does a big defnition = a general slow down?

Hello,

Has anyone noticed that grasshopper will significantly slow down once a definition reaches a certain size?

I have been working on a few quite big definitions recently - and can see my heaviest components (usually offset curves on curved surface), however i noticed on more than one occasion a general slow down that occurs when simply placing components and when plugging them in, where the window freezes for between 1-3 seconds.

Even after placing some relatively light components - whilst it had been working perfectly for a few days, and the whole definition then seemed to operate at about a 1/4 of the speed it should. This also happens when I disable parts of the definition.

Even just putting down a single component now seems to take an excessive amount of time.

Im working on rhino 5, 64 bit i7, nvidia 2gb etc. 8gb ram so I cant understand whats causing it or if there is some relationship to the number of components that causes this apparent stalling.

Any advice or experiences appreciated.

Chris

Views: 5686

Replies to This Discussion

Permalink Reply by phillip on April 16, 2013 at 3:49am

Similar problem occurs again. 

Everytime I wire up a new component it´s taking up to 2 seconds.

No problem with ctrl+c, ctrl+v though.

To avoid the delay by UI I clustered a lot, but it didn´t help much.

The file got quite huge now (3mb) and I wondered why.

So I found out there are some params which still have stored some data which I internalised at a earlier stage and just reconnected them without clearing the values. 

I am pretty sure this is causing the slow down.

Now I can´t select them all and do ´clear values´, so do I have to go thrue the entire file and check every component for internalised data?

What else could I do?

(This would be another application for the heat map, are you still up to this?)

Permalink Reply by phillip on April 16, 2013 at 7:16am

Ok, so there where some needles in that haystack. 

Anyhow, the file is a two thirds now, but thats still quite haevy and still hard to operate.

If it is, as said, just depending on the preview geometry, this is strange though.

Even with disabling all components the delay is still there.

Permalink Reply by Arthur Mamou-Mani on October 23, 2012 at 9:14am

Thanks for raising this issue Chris,

I got a sudden slow down when using a heavy image in the image sampler myself.

With a 4mb image in the sampler, my GH file jumped to 19mb when it is 5kb without the sampler.

There was a slight delay when plugging wires in for each component which is why I looked at the file size.

RSS

About

Scott Davidson created this Ning Network.

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service