Hi, I have a major issue, that is actually preventing me from even using Visual Jforex at all.

I built a complete strategy without running it at all, based on BBands and time and what not.
Doesn't matter, point is it was complex.

When I ran it....it seemed to take forever, just to process ONE DAY!.... I left it for an hour and it got through 1/4 of one day.

So I thought, wth, maybe its too complex, and if thats so, then why even bother using it, just stick to coding.

So I dumbed it waaaaay down, and just had one moving average with an output.
When I ran in realtime, it worked fine, the output would be echoed constantly to the variable.

But when I did a historical test, again, it took FOREVER to even just start the day, and when it finally did, it still took forever to process.
JUST ONE MOVING AVERAGE!???

Is this a bug?? Or what.
Is the processing done on server?? And would it slow to a crawl if too many people use??
Or is it reliant on my computer (which is an Octo core i7, so shouldnt have any trouble)

Please let me know, as this tool looks AMAZING, but its useless if I cant use it.

Heres a screenshot on how simple my last setup was...
It should ran like lightning...

It takes less than a minute to test the strategy in my computer.

The problem can come from your computer, from you internet connection or more probably from an update being perform on our servers at the time of your test.

As we are still in Beta, it could happened several times during the week.

Please try again and let us know.

Greetings.

The main and the only reason on such lagging is using onTick trigger with pile of calculation blocks.
That method loads your CPU hardly. New tick happens from 1 to 10 times per second. And program calculates the same indicator every time.
But SMA(30) on 10min chart would not change a lot from tick to tick.
Use onTick trigger wisely.

Best regards, Support team.

Also if you load the strategy into Jforex - you can use the historical tester and choose what ticks to load. I personally use every tick that changes the price - it is fare more effective than loading 1000 ticks where the price stays the same.

The workaround so far for me, has been to just copy and paste the Java code from my compiled strat, and run it in the actual Jforex platform.
It works there....

But is this a known bug in Visual JF?
Or is it just because its still in Beta?

Cuz it would be nice to just do the testing in the app....but I suppose its not that big a deal to switch back and forth.

We tried to reproduce your problem, but we could not.

We test your strategy in the Visual JForex tool without ant problem.

Yeah, well thanks for trying anyways...
The workaround works for me just fine, and infact i like it better, because after exporting basic structure, I can just play with code from there on out.
Instead of going back into Visual JForex.


But......
The funny thing is that when I tried it at work, it worked in Visual platform just fine.....and the computer there is only 2G Ram, Core i3.

My computer at home is Core i7 Octo-Core, with 16G ram. And it doesn't work.

Logic says the faster computer should work better.....no?

i dunno......oh well.