Minimum delay between server connections

vaughan · 2005-01-24, 04:26

In the ecmclient.cfg file it contains the following:

// Minimum delay between server connections
// (default is 12 hours, minimum is 1 minute)
// Note that the actual used in the client is anywhere from 90% to 110% of this value
maxfreq=30

What does the 30 refer to? Hours, minutes or what? It says default is 12 hours yet this value is 30.

vaughan
AMD Users
www.amdusers.com

wblipp · 2005-01-24, 04:55

Quote:

Originally Posted by vaughan

In the ecmclient.cfg file it contains the following:

// Minimum delay between server connections
// (default is 12 hours, minimum is 1 minute)
// Note that the actual used in the client is anywhere from 90% to 110% of this value
maxfreq=30

What does the 30 refer to? Hours, minutes or what?

Minutes. The original release had 720 as the value, making it an easier guess. I changed the default for the ElevenSmooth set and didn't change the comment. Sorry about the confusion.

vaughan · 2005-01-25, 04:31

No problem, thanks for the reply. Trust a newbie to stumble upon such things heh!?

ValerieVonck · 2005-01-26, 17:22

wich is the "optimal" setting for the client?
- for ecmnet
- for other projects

OmbooHankvald · 2005-09-07, 07:46

Quote:

Originally Posted by CedricVonck

wich is the "optimal" setting for the client?
- for ecmnet
- for other projects

*performing a secret mumbo-jumbo ritual to revive the thread*

I too would like to know this!

wblipp · 2005-09-08, 17:17

It doesn't really make any difference for the vast majority of situations.

A low value causes more frequent connections to the server, but the traffic per connection is very small, so this doesn't really matter unless you are planning to put 1,000 computers onto the project.

A high value might cause you to work longer after another user has found a factor - but factors are rare enough that this isn't much of a problem. A high value might also cause you to run curves at a low level after another user has finished the level - but the transition points are set so that the effectiveness of lower and higher levels are the same, and the additional low curves will be accounted for by needing fewer high curves, so this doesn't really matter, either.

I've only found one situation that makes any difference, and that requires using the new ecmclient that can share among multiple projects. I have access to a few overnight computers, where people manually start the process at the end of their work day and manually end the process the next morning. I want to use these computers for OddPerfect Most Wanted numbers, which typically take 2 hours per curve. My concern is when they kill the program in the morning, all work on the current curve is lost - this could be up to two hours of work.

My solution was to use 8 hours and multiple projects, so that they work for 8-10 hours on the long curves, and then switch to smaller curves on a different project so that less work is lost.

2005-01-24, 04:26	#1
vaughan Jan 2005 Sydney, Australia 14F₁₆ Posts	Minimum delay between server connections In the ecmclient.cfg file it contains the following: // Minimum delay between server connections // (default is 12 hours, minimum is 1 minute) // Note that the actual used in the client is anywhere from 90% to 110% of this value maxfreq=30 What does the 30 refer to? Hours, minutes or what? It says default is 12 hours yet this value is 30. vaughan AMD Users www.amdusers.com

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Connections on this forum	davieddy	Lounge	11	2013-02-22 17:20
What is minimum RAM needed for 6 Core CPU for P-1?	odin	Hardware	15	2010-04-18 14:22
delay in crediting?	ixfd64	PrimeNet	7	2008-10-20 20:45
Why delay between posts?	JHagerson	Forum Feedback	1	2006-05-13 21:30
Stats delay	ltd	Prime Sierpinski Project	10	2005-08-08 13:38

2005-01-25, 04:31	#3
vaughan Jan 2005 Sydney, Australia 5·67 Posts	No problem, thanks for the reply. Trust a newbie to stumble upon such things heh!?

2005-01-26, 17:22	#4
ValerieVonck Mar 2004 Belgium 7×11² Posts	wich is the "optimal" setting for the client? - for ecmnet - for other projects

2005-09-08, 17:17	#6
wblipp "William" May 2003 Near Grandkid 5³·19 Posts	It doesn't really make any difference for the vast majority of situations. A low value causes more frequent connections to the server, but the traffic per connection is very small, so this doesn't really matter unless you are planning to put 1,000 computers onto the project. A high value might cause you to work longer after another user has found a factor - but factors are rare enough that this isn't much of a problem. A high value might also cause you to run curves at a low level after another user has finished the level - but the transition points are set so that the effectiveness of lower and higher levels are the same, and the additional low curves will be accounted for by needing fewer high curves, so this doesn't really matter, either. I've only found one situation that makes any difference, and that requires using the new ecmclient that can share among multiple projects. I have access to a few overnight computers, where people manually start the process at the end of their work day and manually end the process the next morning. I want to use these computers for OddPerfect Most Wanted numbers, which typically take 2 hours per curve. My concern is when they kill the program in the morning, all work on the current curve is lost - this could be up to two hours of work. My solution was to use 8 hours and multiple projects, so that they work for 8-10 hours on the long curves, and then switch to smaller curves on a different project so that less work is lost.