Forum Discussion
FICO
3 years agoCommunity Manager
__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...
FICO
3 years agoCommunity Manager
I am not denying that there is bottleneck with the mutexes. I am trying to understand what causes this bottleneck and what are the situations in which multiple threads would acquire a global lock.
I don't think you broke anything by switching to single-threaded. Xpress parses /proc/meminfo. If this happens from many different threads at the same time, then it is not out of question that you get an EMFILE (24, "too many open files") error. It seems that now many threads attempt to access this file simultaneously and hit this limit. Would it be an option to increase the limit on open files to work around this problem?
Alternatively, could you set the TREEMEMORYLIMIT control (see https://www.fico.com/fico-xpress-optimization/docs/latest/solver/optimizer/HTML/TREEMEMORYLIMIT.html)? That should cut back on the reading of /proc/meminfo.
Related Content
Related Content
Parameter Threads
Hi, I'm using Fico Xpress and I have a question about the parameter THREADS. According to the documentation, THREADS > 0 means the "number of threads to use". Let suppose THREADS = 4. In this ca...7 years agoPlace FICO® Xpress Optimization ForumFICO® Xpress Optimization Forum2 unread comments2 unread0Views0likes2CommentsConst correctness and thread safety in the C-API
How do I know : Which functions can be considered const i.e leave the XPRSprob in an unaltered state ? Which functions are thread safe ? (I am in particular interested in knowing if XPRSbtran and...3 years agoPlace FICO® Xpress Optimization ForumFICO® Xpress Optimization Forum3 unread comments3 unread0Views0likes3Comments