Re: Mersenne: PrimeNet server unavailable?
On Wed, Jul 09, 2003 at 10:03:56AM +0300, Oleg V.Cat wrote: > Hmm... MB this is an answer: > > > > What does PrimeNet error 12002 mean? > > The message forwarding process at Entropia is down. Version 21 > clients and earlier sends messages to entropia.com which are then > forwarded to mersenne.org. Version 22 clients and later send messages > directly to mersenne.org. The best solution is to get version 22 or later. > Alternatively, you can wait for Entropia's message forwarding process to > be restarted which can take several days. > > Thanks - that looks useful. I'd looked at the entry for 2250 errors (which are what the clients report) but not seen that one. I suspect when I look around I'll find that the clients which are failing to report are all running v21. Mass upgrade time! Robin -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: PrimeNet server unavailable?
Anyone else having trouble reaching the PrimeNet server? Several of my clients have been unable to check in for several days, although some did manage last night. At the moment it looks as though the clients are attempting TCP port 80 connections to 66.45.51.160 (no rDNS), which fail. Robin -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: servers down completely?
On Sun, Mar 23, 2003 at 10:11:08AM -0800, John R Pierce wrote: > I can't even raise the mersenne website. getting errors on > entropia.com/ips too, yet entropia.com's home page comes up fine. traceroute shows a nice loop: $ traceroute www.mersenne.org traceroute to www.mersenne.org (216.120.70.80), 30 hops max, 38 byte packets [snippage] 25 ctshub8.cts.com (209.68.192.248) 259.919 ms 268.607 ms 259.904 ms 26 ctshub-f0.cts.com (209.68.192.250) 259.924 ms 258.805 ms 259.909 ms 27 ctshub8.cts.com (209.68.192.248) 259.901 ms 278.746 ms 259.917 ms 28 ctshub-f0.cts.com (209.68.192.250) 279.896 ms 258.750 ms 249.915 ms 29 ctshub8.cts.com (209.68.192.248) 259.907 ms 258.745 ms 259.924 ms 30 ctshub-f0.cts.com (209.68.192.250) 249.890 ms 258.748 ms 259.916 ms And here's my home machine for once dialled up and with results to submit... -- ------- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Prime95 version 23.1 - Pentium 4 improvements
On Sun, Feb 09, 2003 at 09:44:05PM -0500, George Woltman wrote: > 4) A 900 MHz P-III is now required to get first time LL tests by default. Signs your CPU is no longer "cutting edge" technology #23: it no longer gets first-time LL tests by default :-) Out of interest, where's the threshold for factoring/double checks these days? -- ------- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: electrical energy needed to run a LL-Test?
On Sat, Apr 27, 2002 at 05:06:40PM +, Brian J. Beesley wrote: > In terms of P90 CPU hours per kWh, we've got to be looking at P4 Northwood > based systems - equipped with minimum peripherals. The main power saving that > most people can make is to use an LCD monitor instead of a CRT. Better still, switch the monitor off when you're not using it :-) I'm amazed at work at how many monitors seem to be on permanently, not even entering power-saving mode. What a waste - at least a CPU can do something more useful than providing visual entertainment for the spiders. I estimate that my personal system uses a little under 100W with monitor switched off, equating to about UKP1.00 a week at my electricity costs. This system is Duron 700, twin hard disks but one kept powered down by default (primarily on grounds of noisiness!), modest graphics card compared to a lot of modern systems, CDRW and DAT idling - fewer peripherals etc and you might save a few watts, maybe another 10W if you can manage without any disk spinning permanently. The power consumption of the CPU is supposedly around 30W under load - modest compared to recent Athlons or 0.18 micron P4s. > A 15" LCD monitor will use 150W-200W less power than a 17" CRT which has > a similar visible screen size. There's a worthwhile saving in desk space > as well. I did the calculations a few months ago and it's actually a saving of around 100W (my 17" Iiyama claims to take 130W, 15" LCDs seem to take around 30W). I used this to show that replacing CRTs with LCDs purely to lower power bills wasn't yet economic. (And 1024x768 resolution isn't enough for me anyway :-) -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Work being wasted
On Sun, Feb 03, 2002 at 08:06:27PM -, [EMAIL PROTECTED] wrote: > As for Mary's current predicament, with that block of small > exponents you have, my best suggestion is to reverse the order of > the lines in worktodo.ini so that the _largest_ ones are done first. > Intermediate checkins to PrimeNet will then cause unstarted > assignments which are no longer neccessary to be automatically > removed. Of course if one _keeps_ doing this, then the smallest exponents never get processed (and perhaps they become more likely to be poached) :-) -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: variable iteration speeds
On Wed, Jan 16, 2002 at 06:11:49PM -, [EMAIL PROTECTED] wrote: > On 15 Jan 2002, at 22:00, Robin Stevens wrote: > > On an otherwise idle Linux system, I've been noticing that the > > per-iteration speed has been varying during the course of a single > > primality test. Until Saturday afternoon I'd been getting a fairly > > consistent 0.188/0.189s time when the system was idle. It then increased > > to around 0.206s. It fell again last night to around 0.199s (see logs > > below - percentages trimmed for 80-character neatness). > > With stop/start or system reboots between? No restarts other than a system reboot on Sunday afternoon (to sort out a temperamental SCSI peripheral) - across which the speed seemingly remained constant. > Probably the reason for the variability has something to do with the > way the program code and data get assigned to physical memory > locations. BTW Prime95 behaves similarly under Windows. My suspicion is that at some point the system was swapping slightly and the memory location of part of the program or the data changed. -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: variable iteration speeds
On an otherwise idle Linux system, I've been noticing that the per-iteration speed has been varying during the course of a single primality test. Until Saturday afternoon I'd been getting a fairly consistent 0.188/0.189s time when the system was idle. It then increased to around 0.206s. It fell again last night to around 0.199s (see logs below - percentages trimmed for 80-character neatness). Any ideas? It's a Duron 700 desktop system with 512MB PC133 RAM. All I can think of is that something is having a small but noticeable affect on memory access speeds. I can't think of anything I've changed over the past few days on the system: kernel, libraries, etc are all the same. Not a major problem, I'm just curious :-) [Jan 12 02:52] Iteration: 475 / 13355561 Per iteration time: 0.190 sec. [Jan 12 05:29] Iteration: 480 / 13355561 Per iteration time: 0.189 sec. [Jan 12 08:07] Iteration: 485 / 13355561 Per iteration time: 0.189 sec. [Jan 12 10:48] Iteration: 490 / 13355561 Per iteration time: 0.193 sec. [Jan 12 13:34] Iteration: 495 / 13355561 Per iteration time: 0.199 sec. [Jan 12 16:26] Iteration: 500 / 13355561 Per iteration time: 0.207 sec. [Jan 12 19:20] Iteration: 505 / 13355561 Per iteration time: 0.208 sec. [Jan 12 22:13] Iteration: 510 / 13355561 Per iteration time: 0.208 sec. [Jan 13 01:07] Iteration: 515 / 13355561 Per iteration time: 0.208 sec. [Jan 14 11:05] Iteration: 575 / 13355561 Per iteration time: 0.199 sec. [Jan 14 13:51] Iteration: 580 / 13355561 Per iteration time: 0.199 sec. [Jan 14 16:37] Iteration: 585 / 13355561 Per iteration time: 0.199 sec. [Jan 14 19:24] Iteration: 590 / 13355561 Per iteration time: 0.200 sec. [Jan 14 22:11] Iteration: 595 / 13355561 Per iteration time: 0.200 sec. [Jan 15 00:53] Iteration: 600 / 13355561 Per iteration time: 0.194 sec. [Jan 15 03:35] Iteration: 605 / 13355561 Per iteration time: 0.194 sec. [Jan 15 06:16] Iteration: 610 / 13355561 Per iteration time: 0.194 sec. -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Preventing new assignments
On Sat, Jan 12, 2002 at 10:27:48AM -0500, Paradox wrote: > In about 10 days, I've got 5 Pentium4 computers that will be submitting > completed LL tests (for 10,000,000 digit numbers). I used to have dozens > of smaller computers working on such LL tests for years, and so I have a > collection of Prime95/mprime directories which have 60% to 80% completed > LL tests in them. I'm going to want to make sure that the currently > running mprime's on the P4s do not get new assignments, so that I can > simply remove those copies of mprime and replace it with a copy from my > collection. > > For now, I've set the "Days of Work" to 1. If I were to set days of work > to 0, what would happen? How can I tell it to simply submit the results > to primenet, disconnect, and then exit the program when it is done? There should be no need to do this. On the old machines, stop mprime, and copy the mprime backup files (p, and q if it exists) to the machine you want to continue their tests. Then add in the relevant lines from worktodo.ini on the old machines to that on the new one. The machine should then pick up the outstanding tests where the previous machines left off. Keep the existing Days of Work settings on the new machines - once they've exhausted the leftover assignments they will then go back to doing new assignments as before. I've used this method a few times in the past when I've temporarily had mprime running on machines during testing, prior to their being installed as major servers, and have had to transfer unfinished work elsewhere :-) -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: new milestone
On Tue, Jan 08, 2002 at 09:47:36AM +0100, Henk Stokhorst wrote: > [-- text/html is unsupported (use 'v' to view this part) --] Hmmm. Any chance of keeping this list text-only, please? :-) -- ------- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Re: Munich prime party report
On Mon, Dec 31, 2001 at 07:11:33PM -0500, [EMAIL PROTECTED] wrote: > >In case there is no new mersenne prime found in the near future, we plan to > >make this an annual event - or semiannual, or quarterly, or however often we > >can get together. > > Speaking for the California chapter, a get-together to celebrate each new > prime (assuming we don't run into a huge gap By Sod's Law, you'd call a party during a long gap and the next prime would then turn up. Unfortunately, similar laws would prevent one from using this effect to speed up the search, which is a pity :-) -- --- Robin Stevens <[EMAIL PROTECTED]> - Oxford University Computing Services --- Web: http://www.cynic.org.uk/ --- (+44)(0)1865: 273212 (work) 273275 (fax) Mobile: 07776 235326 --- _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: glitches in mprime v19?
On Mon, Oct 11, 1999 at 12:06:07PM -0500, jason wrote: > Well, I also downloaded mprime.tar.gz, and I had a slightly different > problem trying to connect to the PrimeNet server. To summarize: > > mprime.tar.gz v19.0.2: results in "ERROR: Primenet error 1" > sprime.tar.gz v19.0.2: results in "Error 2250: Server unavailable" > mprime.tar.gz v18.1.2: No problems. > > I wonder why the two versions give different error messages (and why I'm > getting them at all)? Anyway, I just compiled mprime from source > (debugging not enabled), and it's working just fine. Except for the fact > that I will not receive credit for my work, since I compiled it myself... > so much for initiative. :-) Indeed - this is the problem I reported a little while ago (again with sprime, since I don't have glibc 2.1 as yet). If v19 works faster, I might as well use it even if I can't currently report results. My temporary solution has been to grab 90 days' of work, switch the machines to run as dialup hosts even if they aren't, and wait for someone else to fix it, reporting via the web interface if necessary :-) -- Robin Stevens <[EMAIL PROTECTED]> http://www-astro.physics.ox.ac.uk/~rejs/ (+44) (0)1865: 273212 (work) 726796 (home) 273275 (fax) Pager: 0839 629682 Oxford University Computing Services, 13 Banbury Road, Oxford OX2 6NN, UK "Life, loathe it or ignore it, you can't like it." -- Marvin _ Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Linux error 2250 (was Front-end design)
On Thu, Sep 23, 1999 at 05:45:39PM -0400, George Woltman wrote: > >Incidentally, can anyone explain why under v19.0.2 I'm getting "ERROR 2250: > >Server unavailable" messages? > Someone told me that glibc-2.1 (as compared to v18's libc5) uses different > files or network setup or something. I am a Linux know-nothing, so perhaps > a list member can enlighten all of us. I'm no expert I'm afraid, but I've done a little more investigating. I grabbed the source and recompiled primenet.c with the _DEBUG option. Of course it now works fine (except it insisted on sending off a load of old results going back as far as May, which according to the logs had definitely been reported before). So I've got the results updated, but without finding the cause of the problem... Oh well, it now works, so I've put v19 on all machines of mine (pity I had to kill off a process with over 100 days' CPU time to its credit (-: ). One point - there seem to be inconsistencies in the case of some of the source file names, which required either manual changing or use of a FAT partition in order to get mprime to compile :-) -- Robin Stevens <[EMAIL PROTECTED]> Merton College, Oxford OX1 4JD, UK http://www-astro.physics.ox.ac.uk/~rejs/ _ Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Front-end design
On Thu, Sep 23, 1999 at 01:53:33PM +0200, Alexander Kruppa wrote: > Robert van der Peijl wrote: > > He further writes: > > There are some Linux folks that like the present program because it > > doesn't use X-windows. > I certainly do! A program like mprime that is supposed to run in > background at all times should not depend on a X server running. Quite. For a start, some of the servers on which I have mprime running don't have an X server. I'm not always logged into them, and X on my desktop machine has been known to be less than fully stable (curse netscape for taking down first X and then the entire machine the other day). Meanwhile mprime can remain running for months without requiring a restart. > Maybe the setup could be handled similar to the NT service version, with > the actual client running without screen I/O in background, and a GUI > program to handle .ini file setting, Status reports, etc. Personally I don't see a need, but I can see that some people might (I saw some 95 boxes the other day running the SETI screensaver, and it does look quite slick). The mprime console program is fine, except that there are now too many options for them to be displayed on a standard 80x24 window or console - perhaps things could be rearranged slightly? Incidentally, can anyone explain why under v19.0.2 I'm getting "ERROR 2250: Server unavailable" messages? Since 18.1.2 as running on another machine has no problems, it's evidently not a case of the server being down. The FAQ mentions a problem on v18 for those using RPC, but I was under the impression I've always been using http... -- Robin Stevens <[EMAIL PROTECTED]> Merton College, Oxford OX1 4JD, UK http://www-astro.physics.ox.ac.uk/~rejs/ (+44) (0)1865: 726796 (home) 273337 (work) 273390 (fax)Pager: 0839 629682 When puns are outlawed only outlaws will have puns. _ Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Linux VFAT question
On Sun, 27 Jun 1999 11:45:37 -0400, Pierre Abbat <[EMAIL PROTECTED]> wrote: > > But the fact is that the performance of my mounted hdd win98 (vfat) > > partition is very low. All my normal linux (ext2) partitions work with > > normal performance. > > cd to various directories, then type vdir|wc -l in each. This tells you > how many files the directory has. The more files, the longer it takes to > sort them. vdir -U lists the directory without sorting it, which is a > little faster. I too find that performance on fat/vfat partitions is low compared to ext2 partitions, but I don't think that's too surprising: the kernel is understandably optimised for ext2, and FAT partitions are hardly the most efficient of filesystems in the first place. To be honest, I don't see a lot of difference in performance on fat partitions whether or not mprime is running. > mprime just writes once every 30 minutes, so whether it's running in the > Windows drive or the Linux drive is inconsequential. As to the swapping, > the swap daemon runs at 12 naughty, so I don't see why mprime at 20 nice > would bother it at all. On one of my machines, disk performance appears significantly worse with mprime running than when it's switched off. On my P200MMX, performance on a Quantum Fireball ST4.3A drops from about 8.25MB/s to 4.9MB/s (measured using hdparm). However the performance of the Seagate drive on the same machine and the Fujitsu drive on my PII-266 is barely affected by mprime. Still, I'd rather lose a little on disk performance than waste over 96% of my workstation's CPU cycles :-) One write every 30 minutes is hardly going to trouble things much. I'd far rather have the machine doing regular disk writes than risk losing several weeks' (your uptime may vary) work if mprime is not terminated neatly. -- Robin Stevens <[EMAIL PROTECTED]> Merton College, Oxford OX1 4JD, UK http://www-astro.physics.ox.ac.uk/~rejs/ (+44) (0)1865: 726796 (home) 273337 (work) 273390 (fax)Pager: 0839 629682 Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne: HTML posts
On Tue, May 18, 1999 at 03:43:06PM -0700, Mersenne Digest wrote: > - --2F0C58BF3B6CAD96679EFF20 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit [snip post in nice ascii text] > - --2F0C58BF3B6CAD96679EFF20 > Content-Type: text/html; charset=us-ascii > Content-Transfer-Encoding: 7bit > > > [snip repeat of the above but in HTML] Apologies for the off-topic post, but could I please request that people posting to this list do so in plain text format and not HTML? There have been several such posts of late. It's incredibly irritating to those with less advanced mail programs, or to those who read the digest. Please pay a visit to http://www.rootsweb.com/rootsweb/listowners/html-off.htm if you don't know how to configure your mail client appropriately. -- Robin Stevens <[EMAIL PROTECTED]> Merton College, Oxford OX1 4JD, UK http://www-astro.physics.ox.ac.uk/~rejs/ (+44) (0)1865: 726796 (home) 273337 (work) 273390 (fax)Pager: 0839 629682 Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Re: Mersenne: cacheable memory
On Sun, May 16, 1999 at 05:22:59PM -0700, Mersenne Digest wrote: > Date: Sun, 16 May 1999 16:57:08 -0700 > From: Kevin Sexton <[EMAIL PROTECTED]> > > Anybody know which chipsets have the memory caching problems, or who can > point me in the direction to find this information? Intel chipsetted Pentium boards are the chief offenders: the FX, VX and TX all being unable to cache more than 64MB. Some HX boards can cache up to 512MB by default, others require additional tag RAM to cache above 64MB. Some HX boards (like mine) don't have a socket for inserting tag RAM :-( If you have one of the more recent Socket7/Super7 chipsets from SiS or VIA, I believe they'll happily cache up to 256MB or 512MB. Pentium IIs are fine up to 512MB IIRC, so it'll probably be a year or two before that becomes a problem for significant numbers of people. I've just put my P200MMX system up from 64MB to 160MB and find the impact on GIMPs performance under Linux to be at about the 2% level, which I can live with. To be fair I am doing double checking on this machine - the performance drop may be greater for exponents in the 7-8 million range than for those around 3 million. > I am interested in finding out whether to add memory to a VXPro board, > currently has 32MB, AMD K-6 200. I know this is not strictly on topic, > but it might increase performance of prime95, especially if another app > hogs the memory I have now. It's probably worth it - 32MB is not a lot these days ;-) -- Robin Stevens <[EMAIL PROTECTED]> Merton College, Oxford OX1 4JD, UK http://www-astro.physics.ox.ac.uk/~rejs/ (+44) (0)1865: 726796 (home) 273337 (work) 273390 (fax)Pager: 0839 629682 "He's dead Jim." "I know, Bones. I've seen the script" Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne: Performance hit on Pentiums with >64MB?
I currently have a P200MMX with 64MB running Primenet under Linux. Finding 64MB rather limiting on my desktop workstation, I'm looking to equip the machine with a couple of 64MB SIMMs. However I shall be running into the limitation of most Pentium motherboards in that the machine will be unable to cache more than 64MB of RAM. How much of a performance hit am I likely to encounter in running Primenet? I've seen figures of 10-30% quoted for various applications. Not that I'm overly bothered - I have a PII contributing rather more these days :-) -- -------- Robin Stevens <[EMAIL PROTECTED]> Merton College, Oxford OX1 4JD, UK http://www-astro.physics.ox.ac.uk/~rejs/ "Never attribute to malice what can be explained by incompetence." Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
