[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-glpk] Multi-thread questions

From: Paolo Bolzoni
Subject: Re: [Help-glpk] Multi-thread questions
Date: Fri, 11 Oct 2013 14:02:05 +0200

I guess, but I would like more to use the C API
to avoid to implement all the serialization of the input and
deserialization of the output.

Another solution we thought is executing a process
that reads the input from stdin and writes to stdout
the objective. But still, if we can avoid to serialize and
deserialize is better.

On Fri, Oct 11, 2013 at 1:54 PM, Meketon, Marc
<address@hidden> wrote:
> One easy form of parallelization involves using "glpsol" (the command-line 
> version of GLPK) instead of calling the API.  Have the controlling program 
> launch multiple "system" windows that execute glpsol.  That way each run 
> maintains its own memory space.
> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of Paolo Bolzoni
> Sent: Friday, October 11, 2013 7:31 AM
> To: address@hidden
> Subject: [Help-glpk] Multi-thread questions
> Dear list,
> the Reference Manual of Version 4.38 states that GLPK routines are 
> non-reentrant and so they cannot be used in multi-thread programs.
> I was wondering, it is at least possible to solve two different problems in 
> two different threads?
> In my scenario, I have many linear problems and I have to find the one with 
> the maximum solution. Parallelism is easy for this scenario since there is 
> nothing to share, just find the best.
> I read there are previous email in this list about multi-thread safety, but 
> they are fairly old. So I prefer to send a new one. Thanks.
> Yours faithfully,
> Paolo
> _______________________________________________
> Help-glpk mailing list
> address@hidden
> This e-mail and any attachments may be confidential or legally privileged. If 
> you received this message in error or are not the intended recipient, you 
> should destroy the e-mail message and any attachments or copies, and you are 
> prohibited from retaining, distributing, disclosing or using any information 
> contained herein.  Please inform us of the erroneous delivery by return 
> e-mail. Thank you for your cooperation.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]