Forum Discussion
__lll_lock_wait allowing only one thread to work
I am calling the XPRESS optimizer from a multithreaded Pascal application and having performance issues with the solver. While the program is multithreaded, all but one of the threads are sleeping a...
Several threads build their problem and optimize them in a concurrent fashion. While each of the threads do create and destroy several problems, a comparison with an open source solver that's also integrated with the application yields a CPU usage 30 times higher and much faster execution times.
The debug clearly shows threads are waiting for a mutex. There must be a bug in the program for sure, I just need to figure out why XPRESS would wrap destroyprob around a mutex and why I am hitting it as it would make sense that such operation could be done in parallel.