#12736: More solver options for GLPK
--------------------------------------+-------------------------------------
Reporter: john_perry | Owner: ncohen
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: linear programming | Resolution:
Keywords: solver parameters | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by john_perry):
Replying to [comment:20 ncohen]:
> I was just looking at the code and thinking that if the user wanted to
set the LAST parameter the code would test all others first. That's why I
would have wanted some dichotomy ! `:-D`
That bothers me, too. I guess it should be organized so that the options
most likely to come first would be tested first -- OR -- organize an if
tree so that we have O(log(n)) comparisons instead of O(n). I'm completely
open to suggestions on that.
> Well, I was just surprised that comparing integers was *that much
shorter* than comparing strings.
I don't have hard tests, but it seems pretty obvious; string comparison is
quite a bit more expensive.
> And that it could become the bottleneck in LP codes `:-)`
Unlikely, of course, but every bit helps `:-)`
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12736#comment:21>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
