If the individual components aren’t too complicated, that shouldn’t be a problem. Handling 100,000 top-level objects should have acceptable performance, as long as you aren’t trying to show them all at once.
Try the application I present in http://www.nwoods.com/forum/forum_posts.asp?TID=1871.
That will show a random number (around 100,000) of GoBasicNodes and GoLinks, each with random colors.
Since it creates the nodes on demand, it starts very quickly. Scrolling is pretty good too. Dragging around a node is pretty snappy also.
If you do zoom out to show the whole grid, it will take time to construct all of the nodes and links. Dragging around a node (which is hard to see at such a small scale) is slow, but I think the performance is pretty good considering how many nodes and links are visible simultaneously. But if you try selecting several thousand objects at once and drag them around, you’ll definitely see the lag.
But if each of your components has hundreds of nested objects, you’ll probably have a lower effective limit. Still, if the components are distributed in space and your view is only showing a small fraction of them, responsiveness should be good.
Thank you very much. A convincing argument! My problems clearly lie in other areas of the code, not with Go. That is reassuring :)