This has been the default behavior since we created the IIS setup guide (as far as I know). Basically, we had to add a flag to tell rhino.compute whether or not it should launch an instance of compute.geometry when it starts up. When you’re running rhino.compute locally, this is the default behavior. However, when you’re running rhino.compute on a remote VM, what we found was idle webcrawler traffic that was hitting on port 80 was causing IIS to spin up an instance of rhino.compute and then it would automatically launch a child instance of compute.geometry… even if you weren’t the one who sent the request (it was just a web crawler who kicked everything off). So, we added a flag to the project which would tell rhino.compute to only spin up a child instance whenever a true authenticated request got sent to it. So, if you call the /activechildren endpoint, it will do as you said… it will call InitializeChildren which will start trying to spin up as many children as you have specified. The /idlespan timer will then start from there. If you want to test whether the rhino.compute server is up and working, but don’t want to spin up a child, you can use the /healthcheck endpoint. Does that help clarify things?
4 Likes