Re: [Help-glpk] out-of-memory workarounds [Fixed]

[Andrew Makhorin]

> Replying to my own email:

> I've added a table lookup that converts my handy-but-VERY-sparse
> indexing into a much more compact form. As I have a wrapper library
> for the glpk calls, I was able to localize all of the changes there
> and not touch (much) of my application code.

> The presolver is now not eliminating any rows or columns, and we're
> going to call that a good thing.

>> lpx_simplex: original LP has 775626 rows, 3861761 columns, 302081
>> non-zeros
>> lpx_simplex: presolved LP has 18378 rows, 75520 columns,
>> 302080 non-zeros

The number of non-zeros is the same in both cases, so obviously many
rows and columns are empty.

>> lpx_simplex: original LP has 1319436 rows, 6581761 columns, 163841
>> non-zeros
>> umalloc: size = 8024; no memory available

This means that malloc returned NULL, i.e. the program exhausted all
available memory.