search

sate-dev / sate-core

3 stars 3 forks source link

max_mem_mb does not get propagated to opal on command line #34

Closed smirarab closed 11 years ago

smirarab commented 11 years ago

In command line mode, max_mem_mb does not get set for opal merge jobs. The reason is pretty simply. In Usersettingclass, under create_merger, the dictionary that is created and passed to initializer of a merger class is created based on settings under the name of that specific tool. So, for opal, what's under opal heading in the config file will be passed to opal. max_mem_mb is defined under sate category. As a result, it is never actually passed to opal, and only the default (1024) is used.

Proposed solution: move max_mem_mb to opal. Alternatively, change create_merge so that global settings are also grabbed.

smirarab commented 11 years ago

false alarm! I was testing a wrong version of sate