What are the hardware bottlenecks for Unity (the editor)?

Questions & Answers
1

Hi there,

I’ve been doing some Unity development on my NC10 netbook while on the train, and my normally trustworthy little friend (capable of doing J2EE or Android development on Eclipse!) has finally met his match in the hardware department. Everything feels pretty sluggish in the editor, and opening files in Mono Develop always takes 10-20 seconds even with Mono Develop already open. I notice when I actually launch the game, the framerate is pretty decent - it’s the editor and IDE that are slowing me down.

I’m not sure if this question has an easy answer, but I’m trying to figure out whether to shove more RAM and/or a SSD hard drive in it, or fork out for a new netbook/laptop. What are the main hardware bottlenecks for Unity’s editor and IDE? Is it I/O, CPU, RAM, or a combination?

Thanks!

2

It may be because Unity and Mono are checking the integrity of project files, import them, verify syntax, update instances… almost each time you are doing something. There are a lot of calls on the hard drive to read and verify. But when you launch the game, we could say that it has to be fast because it runs on RAM.

But these are only hypothesis from my experience.