Resetting projected finish dates

Kevin · 2003-07-06, 17:31

What do I set RollingStartTime and Rolling Average equal to in local.ini to reset the projected finish dates? It always gets screwed up after I run Prime95 as a back-up to some other project.

Prime Monster · 2003-07-06, 19:20

Just leave them, they are automatically adjusted by the client.

trif · 2003-07-06, 22:02

Quote:

Originally Posted by Kevin

What do I set RollingStartTime and Rolling Average equal to in local.ini to reset the projected finish dates? It always gets screwed up after I run Prime95 as a back-up to some other project.

If you had Prime95 running as a backup to something else, and are going to be running it as the primary now, it would be reasonable to reset it. You don't need to muck with the RollingStartTime. Exit Prime95 (don't just stop it, you have to completely exit). If the machine is going to never be doing anything but Prime95, set RollingAverage to 1000. If it stays on all the time, but you do stuff on the machine, use a value like 800. If it is on for 12 hours a day, try 500. Prime95 will then make finer adjustments after that based on how much work Prime95 actually gets. Restart Prime95 after saving the file.

Xyzzy · 2003-07-06, 22:31

I think you can just delete that line and Prime95 will generate a new one for you...

Kevin · 2003-07-06, 22:41

Alright, I deleted the lines, restarted Prime95, and all is back to normal.

Reboot It · 2003-07-07, 13:42

Two points I have discovered for those that are interested in this kind of thing:

1) The RollingAverage value is capped at 4000.

This can have an effect if for example you have estimated that the PC will be on for say 5 hours per day and it turns out that the user leaves it switched on 24/7. The RA value increases over time and gets stuck at 4000, so the estimated completion times will always be too long and the amount of work cached will be correspondingly too small. This effect would be worse if the number of hours had been set smaller to 2 or maybe even 1 hour of use per day.

2) Simply changing the "Hours per day this program will run" value will also reset the RollingAverage value to 1000 for you - without the need to mess around with exiting, editing the LOCAL.INI file and restarting the client.

2003-07-06, 17:31	#1
Kevin Aug 2002 Ann Arbor, MI 433 Posts	Resetting projected finish dates What do I set RollingStartTime and Rolling Average equal to in local.ini to reset the projected finish dates? It always gets screwed up after I run Prime95 as a back-up to some other project.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Projected results of sea level rise	kladner	Soap Box	14	2014-07-18 06:36
User-based computer that NEVER needs resetting, possible?	jasong	jasong	11	2013-08-06 09:51
Projected Pictures.	mfgoode	Puzzles	18	2007-09-21 08:06
Prime95 resetting LL test	jonthomson	Software	17	2007-05-12 13:21
where do TF go when they finish?	markr	Data	5	2005-03-09 05:19

2003-07-06, 19:20	#2
Prime Monster Aug 2002 100000100₂ Posts	Just leave them, they are automatically adjusted by the client.

2003-07-06, 22:31	#4
Xyzzy Aug 2002 10000101101101₂ Posts	I think you can just delete that line and Prime95 will generate a new one for you...

2003-07-06, 22:41	#5
Kevin Aug 2002 Ann Arbor, MI 433 Posts	Alright, I deleted the lines, restarted Prime95, and all is back to normal.

2003-07-07, 13:42	#6
Reboot It Aug 2002 London, UK 3×31 Posts	Two points I have discovered for those that are interested in this kind of thing: 1) The RollingAverage value is capped at 4000. This can have an effect if for example you have estimated that the PC will be on for say 5 hours per day and it turns out that the user leaves it switched on 24/7. The RA value increases over time and gets stuck at 4000, so the estimated completion times will always be too long and the amount of work cached will be correspondingly too small. This effect would be worse if the number of hours had been set smaller to 2 or maybe even 1 hour of use per day. 2) Simply changing the "Hours per day this program will run" value will also reset the RollingAverage value to 1000 for you - without the need to mess around with exiting, editing the LOCAL.INI file and restarting the client.