Hangs after 1 day 19 hours AND ALL STRATEGIES ARE LOST!

There is an optional file-synchronization in databank, you can set it to synchronize every X minutes, so that you'll not lose your work if program crashes.

Otherwise databank is kept in memory for performance reasons.

We'll look at memory problems during long generation, we'll try to solve it in the next build.

Yes, this was on build 108.

I will look for the file-synchronization option.

A suggestion is to set the file-synchronization ON as default. Considering that you have customers from all over the world running SQ on everything from laptops to data center quality servers I am willing to bet that, being customers and not IT specialists, they are not prepared for an extended power outage and many may be in countries without reliable power. In my case, living in Florida which is the lightning capital of USA, my computers have individual dedicated data center level UPS protection. The fact that my server draws nearly 500 watts when running at max capacity the battery run time is still limited to no more that 10 minutes before the server performs an automatic shutdown. Even with a UPS initiated orderly shutdown I suspect that any strategies that had been found would be lost.

I found the option to store strategies on the hard disk. I do not understand how writing a file to disk could cause a 90% degradation in the generation cycle. If the intent is to maintain a 100% mirror image with memory when the max strategy threshold has been met then I *might* understand. A real simple option is simply to write every single strategy to disk when it is put in the database and do not worry about any strategies that are later deleted.  In other words if my max strategy number is 5 then keep on writing each subsequent strategy to disk even though SQ has already found 5.  Nobody will complain about 25 additional strategies only because they took a weekend holiday.  Likewise, I run SQ with 10,000 allowed strategies and would not be upset if I found 30,000 after a three week period.  Simply stated, don't worry about synchronizing the data, just save it. The user can never recover the lost data but they can always re-analyze the excess data and throw away what they don't want.

Just an idea.

Dave

I found the option to store strategies on the hard disk. I do not understand how writing a file to disk could cause a 90% degradation in the generation cycle. If the intent is to maintain a 100% mirror image with memory when the max strategy threshold has been met then I *might* understand. A real simple option is simply to write every single strategy to disk when it is put in the database and do not worry about any strategies that are later deleted.  In other words if my max strategy number is 5 then keep on writing each subsequent strategy to disk even though SQ has already found 5.  Nobody will complain about 25 additional strategies only because they took a weekend holiday.  Likewise, I run SQ with 10,000 allowed strategies and would not be upset if I found 30,000 after a three week period.  Simply stated, don't worry about synchronizing the data, just save it. The user can never recover the lost data but they can always re-analyze the excess data and throw away what they don't want.

Just an idea.

Dave

But we added periodic synchronization with file system, it is the best from both worlds. We'll make it turned on by default in the next build.

I believe saving strategies once every hour or two must be sufficient.