Project

General

Profile

Actions

Bug #5247

closed

Allow user to set memory allocated to Kepler from within Kepler

Added by Derik Barseghian almost 14 years ago. Updated over 12 years ago.

Status:
Resolved
Priority:
Normal
Category:
general
Target version:
Start date:
11/23/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5247

Description

A nice feature for advanced users would be to let them set how much memory kepler is allocated (presumably a restart would be required for the change to take place).

This is in part motivated by some users who have run workflows that pass large chunks of data around as tokens, and execution has stopped with an error because of heap space errors.

Actions

Also available in: Atom PDF