Closed Village-Guy closed 3 years ago
I have the same. Deepstack opens with 2 python instances per port but it then closes down all but 2, but sometimes all of them. I logged this with Deeptsack months ago but they haven't come up with a solution. It can be very temperamental using multiple ports with the GPU version but then often it runs great. I found increasing the paging file size helped but that could have been coincidence.
Hit Stop, then Start and wait a minute. Send me any recent errors from the log window, and also hit STDERR.TXT button and send me that file if it exists.
For every copy of DeepStack, there should be 2 copies of Python.exe
running. There would be an error if less than 4 copies of python.exe were running in your case since you are using 2 ports. This is what one copy looks like when you use Process Explorer or Process Hacker to see the process tree:
Try cutting it down to 1 port to see if the same thing happens. More than one copy running never seems to be terribly stable for some reason. I recommend trying to find a second device to run the second copy of deepstack on. I run a second copy on my synology NAS and raspberry pi, and am trying to get an nVidia NANO set up for a 3rd.
I have resolved this issue by regressing my system back to running DeepStack inside a Docker environment. It appears more efficient and reliable than running in a Win 10 environment when more than one copy of DeepStack is running on the same processor.
DeepStack page is showing an error but everything seems to be working fine