View Single Post
Old 2008-10-31, 09:14   #2
Old man PrimeNet
 
Old man PrimeNet's Avatar
 
Jan 2003
Altitude>12,500 MSL

101 Posts
Default

For immediate communications please email me the particulars of any issue at primenet@mersenne.org. I respond to email significantly earlier than forum posts.

For participants using or upgrading from Prime95/MPrime v24 or earlier (installed before October 2008), you will need to make a new PrimeNet account and then link your old account to the new account to transfer any accumulated work credits -- please start here: http://www.mersenne.org/gettingstarted/ .

For participants picking your own assignments using the PrimeNet APIs directly for bulk advance TF in particular:
(a) Note that this activity is not encouraged and there's a large probability that in the near future PrimeNet will either restrict or block this kind of activity completely. If your IP gets blocked it means you are not paying attention to your activity's impact on the PrimeNet server's response times and instead it has my attention, and not the good kind.
(b) If your computers are using the native communications and work-type selection features of Prime95 and MPrime, PrimeNet will typically automatically assign them the most useful work for GIMPS' objectives. The worktodo files maintained by the programs are designed to be let alone and queue the work for that computer only, not used as a workload redistribution point using other mechanisms.
(c) If you insist upon doing these things, consider using the Manual Results web forms, which are the intended method for requesting and submitting large numbers of work units the server would not normally assign to your computers.
(d) Lately there has been a noticeable increase in advance, shallow (e.g. rapid) TF unit workload, which is perhaps the least useful work and generates the most network traffic, and is why the server usually will not assign these in significant counts. While we are grateful for all useful contributed computational work, the GIMPS PrimeNet server has and will always have finite resources, and anyone insisting upon doing high-volume race-ahead work of any kind is required to exercise the necessary programming skill and discipline to continuously monitor and dynamically react to the impact of their web API traffic so as to not bog down the entire GIMPS project in pursuit of their personal objectives, ignorantly or otherwise. If response times lengthen significantly or the API repeatedly times-out, your program may be transacting too frequently and should use a back-off rate timing scheme.

Last fiddled with by Old man PrimeNet on 2010-03-13 at 18:13
Old man PrimeNet is offline   Reply With Quote