I don't have another way of contacting you so here goes nothing.

Would you mind considering putting a RAM clearing program into WL6+ such that when you hit Backtest on all symbols in a dataset the memory gets cleared. Right now, the program fails to do that and whenever you test a dataset of 500 symbols and then move to another dataset of 500 symbols it causes wealth-lab to crash. Maybe there are more elegant solutions but I do not know what they are. As I am running 8 gigs of RAM I don't think it is an issue of enough memory.

On a related issue, I wanted to give you a heads up that when you run a backtest on a large dataset and you look at performance By Period some early periods get moved to the back of the display.

Thanks very much for your help and consideration regarding this.

I could've started like "some future release, based on .NET 4.0, would bring in a faster and thus more effective garbage collector" but... What operating system are you running, is it 64-bit? On a 32-bit OS without the /3GB switch, regardless of what RAM size is there, an application can consume just about 2Gb RAM. To overcome this, you need WLP6 64-bit edition running.

Next step is to figure out how much RAM is required. We can't do it for you since you didn't tell any details at all: is it intraday data or daily, what is the data loading range for those 500 symbols, what is the strategy about. Here's a guideline: (scroll down to) Out of memory problems. (As you now understand, this is not just a question of memory size alone.)

QUOTE:
On a related issue, I wanted to give you a heads up that when you run a backtest on a large dataset and you look at performance By Period some early periods get moved to the back of the display.

How exactly does this look like? Take a screenshot, upload it to any image hoster, paste the direct image link in between a pair of IMG tags.

Thanks.

Running 64 bit WLP6 now; prior problems appear to have disappeared.