- ago
With a freshly installed Build 18 (no extensions installed) I run an exhaustive optimization (1000 Iterations) of an optimizable version of Knife Juggler on 10 years of Nasdaq 100 data:



Memory consumption rises quite quick, after a while the CPU usage breaks down and finally WL becomes unresponsive.

Let me know if you need more details.
0
228
Solved
3 Replies

Reply

Bookmark

Sort
- ago
#1
Memory usage stays constant if I use "Exhaustive (non parallel)" optimizer.
(In exactly the same scenario)
0
Glitch8
 ( 10.94% )
- ago
#2
It looks like the same issue that we already rectified that was causing Dolphin's instability issues, it should be stabilized for Build 19.
0
Glitch8
 ( 10.94% )
- ago
#3
Confirmed an improvement to the Exhaustive Optimizer for Build 19, much faster optimizations and much better memory footprint!
3
Best Answer

Reply

Bookmark

Sort