-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compute.geometry.exe not releasing memory #468
Comments
I am using the following settings in web.config because it was spawning 4 processes but it would only every use one and it never recycled any of the processes or shut them down after. Also, my python application which is doing the request to the compute node (running locally) was timing out waiting for the compute.geometry.exe to startup. In this configuration, it still doesnt spawn the compute.geometry.exe process until you connect with valid API connection, so I am having to do a request to the /healthcheck as a way to get it to spawn the process and then do a sleep timer for 20 seconds to wait for it to initialize before it will start taking requests. <aspNetCore processPath=".\rhino.compute.exe" arguments="--port 80 --childcount 1 --spawn-on-startup" stdoutLogEnabled="true" stdoutLogFile="..........\logs\LogFiles\W3SVC1" This is an example of what I am having to do to get this to work for me (python). code from my application I have to run everything before I process a grasshopper script:
code from b2f_grasshopper.py
|
Possible duplicate of #396 ? |
The compute.geometry.exe process spawned by rhino compute running under IIS does not release memory and eventually crashes the server. I have coded a workaround by checking for the working set size each time I send a grasshopper request to the compute node. When the working set gets over 10GB I kill the process and restart the app pool.
The text was updated successfully, but these errors were encountered: