-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query runs out of memory #31
Comments
@pralitp Do we even support 32-bit Java? I feel like everyone who has ever installed it has run into some kind of problem for which the fix is "install 64-bit Java". |
We don't support 32-bit java for running GCAM. However technically you could use it for running the Model Interface / queries via rgcam. It could very well be the case that windows folks have been getting away with running the 32-bit Java with rgcam this whole time and changing the max above 2GB would break them. In which case we would have to figure out how to get R to run the right Java.. which should be possible but I didn't want to dive into that at the moment. |
So, if we don't support 32-bit Java, then we should just up the memory limit in |
This change is incompatible with 32-bit Java. We don't actually support 32-bit Java, but some users may have been getting by with it. This change will break for them. The solution is to upgrade to 64-bit Java. Fixes #31
Raise java memory limit to 4 GB when running model interface. Fixes #31
When running the query "GHG emissions by sector" for all regions, we run out of memory, giving this error:
Changing the memory limit in
runQuery.localDBConn()
from 2GB to 4GB solves this problem for me, but could cause trouble for 32-bit Java.The text was updated successfully, but these errors were encountered: