Reduce forecast run-time?

[stoneygate]

Hi all,

I'm running LS 1.81 trial for UK 6/49 with default forecast 10 @ 100 samples.

My run-time was always around 90 minutes for many forecasts. On one occasion I 'minimised' Lottosync so it was just running in the Taskbar and the run time fell to 45 mins! Since then I always run it in minimised mode and the runtime continues to be approx 45 minutes.

(As a former programmer I suspect the repeated printing of numbers (of the samples) on-screen is quite demanding on the system which isn't necessary when minimised).

Running on 2ghz core2duo Apple iMac > Parallels V3 > XP.

Anyone else notice this? I haven't noticed a similar thread here nor on Lotterypost.

Worth a try as you could potentially double the samples or double the forecasts in the same time

[MillionsWanted]

(01-31-2009 06:41 AM)stoneygate Wrote:  Hi all,

I'm running LS 1.81 trial for UK 6/49 with default forecast 10 @ 100 samples.

My run-time was always around 90 minutes for many forecasts. On one occasion I 'minimised' Lottosync so it was just running in the Taskbar and the run time fell to 45 mins! Since then I always run it in minimised mode and the runtime continues to be approx 45 minutes.

(As a former programmer I suspect the repeated printing of numbers (of the samples) on-screen is quite demanding on the system which isn't necessary when minimised).

Running on 2ghz core2duo Apple iMac > Parallels V3 > XP.

Anyone else notice this? I haven't noticed a similar thread here nor on Lotterypost.

Worth a try as you could potentially double the samples or double the forecasts in the same time

Ok. I'm running a forecast right now. Time is 21:46 CET. It is supposed to be finished 00:23 CET. I have minimized it right now. Let's see if it finishes earlier. Need to open it once in a while to check when it will finish of course. Perhaps it needs a running in the tray function only showing finishing time.

[stoneygate]

(01-31-2009 06:47 AM)MillionsWanted Wrote:  Ok. I'm running a forecast right now. Time is 21:46 CET. It is supposed to be finished 00:23 CET. I have minimized it right now. Let's see if it finishes earlier. Need to open it once in a while to check when it will finish of course.

No need to pop it up as LS displays a dialogue box on-screen when it's finished. Nice.

[MillionsWanted]

Instead of ending 00:23 CET Jan 31 it ended 23:55 CET Jan 30. I had a lot of other software running using resources which can explain why I didn't save so much time.

[stoneygate]

(01-31-2009 09:18 AM)MillionsWanted Wrote:  Instead of ending 00:23 CET Jan 31 it ended 23:55 CET Jan 30. I had a lot of other software running using resources which can explain why I didn't save so much time.

I try to leave my computer alone just running a forecast which may explain the significant time difference.

[Fernando]

I noticed that almost from the beginning, so I always run it minimized, but didn't think to say anything here about it, I use LottoSync almost everyday.
On the old Commodore 64 8 bit computers, if programs turned off the video display the programs would run faster, somebody discovered that, but very few programs used that trick, on those all computers very many programing tricks could be used as they were very flexible, some had to do with using the raster or whatever the word is, I forgot about all those things.

[MillionsWanted]

Gave it a real try today. I let the time "settle" in the beginning before timing the forecast. I timed it at 22:04 CET Jan 31st. Then it said it will finish in 03:43 hours, which means it was supposed to end 01:47 CET Febr 1st. I minimized the program and it finished 00:30 CET Febr 1st. I saved 1 hour and 15 minutes. Not bad. And it might be needed when X400 samples will be introduced in ver. 1.8.2. I had a lot of programs running but still reduced the forecast time by 33%.

[vick]

good tips guys !

[LottoSync]

It's indeed possible that Lottosync forecasts are running faster when it is minimized, but how much time it will save you largely depends on your individual computer system.

Most of the computers we use here for testing run almost equally fast with the window opened or minimized.