Topic: Generator (and Optimizer) memory usage
Apologies if this is covered elsewhere, if so I couldn't find it. I did note the suggestions regarding setting the number of 'threads' to 1; and minimizing logic slots and selected indicators - in a similar Generator memory question.
Firstly, I'm no computer tech expert and I was told previously that my 2012 i7 laptop with 4 gig ram is a bit underpowered these days for a memory intensive application like FSB Generator; and I'm working on a ram upgrade.
I first demo'd FSB in Sept 2014 and I don't recall noticing Generator or Optimizer memory problem then, so I'm wondering if there may be some memory usage issues with the recent version e.g. if it's become more demanding as its complexity has increased or if a problem has crept in somewhere.
Currently, even with the Generator on the bare minimum slots and indicators (set on 1 thread) it starts off OK but gradually within an hour or two the laptop becomes increasingly sluggish and unusable until eventually I have to manually crash it with the power button to restart. Then it requires a second restart to get Win 7 running clean again. My poor baby is getting repeatedly thrashed and I'm concerned about potential Operating System or even Hardware damage - is this a valid concern?
I get the impression that as the Generator (or the Optimizer) works, FSB uses more and more ram with no limitations until it eventually overwhelms the computer. Perhaps it has what I've seen referred to as a 'memory leak'.
I noticed in a recent demo of StrategyQuant's Generator - which also had a similar similarly sluggish effect, there's a button to clear memory while the generator is working which helps a bit.
Ideas from a non-techie (try not to laugh too loud)
- Perhaps there is some (recent) Generator and Optimizer memory usage issue to review.
- Perhaps FSB could utilize temp files that are automatically deleted instead of holding everything in ram (if that's what it does).
- Perhaps some user control to set and limit FSB's memory usage within the constraints of the user's computer.
- Perhaps a 'delete cache button' or 'auto cache clearing'.
I expect the verdict will be 'just throw more ram at the problem' (which is the reply I got to a similar recent question), but the helpful input here is always much appreciated. Also, I thought this feedback may be of some use.