Now though the error message could be understood as "gimme more hardware/memory to get rid of the error" I'd recommend to evaluate a changed strategy in the clustering:
Reduce the planning complexity by applying a pregrouping of locations, e.g. based on post code areas or street names
Best regards,
Bernd
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...
I have discovered this link (https://support.gurobi.com/hc/en-us/art ... -condition) while searching solution on the internet about this issue.
Those suggestions mentioned (1-5), are we able to change the settings for communication between xCluster and the Solver for testing?
Thanks for your question. We chose the values of xServer and gurobi parameters carefully to be able to efficiently solve a variety of instances. So the settings (also those specified by gurobi) cannot be changed.
But as mentioned in gurobi thread, the fundamental problem seems to be insufficient memory, and the best solution would be to increase memory.
Just some fancy experiment... I took almost 10'000 locations with zipcodes and activities.
the native 9288 individual locations
preaggregated into 2779 representing "zips" with accumulated activities
From my perspective you wouldn't loose quality if you aggregate...
But you need less resources.
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...