Posts by Cliff Harding
|
1)
Message boards :
Number crunching :
Don't know where it should go? Stick it here!
(Message 2038239)
Posted 16 Mar 2020 by  Cliff Harding
Post: It seems that folding@home is researching COVID-19 https://www.guru3d.com/news-story/foldinghome-put-your-cpu-and-gpu-in-use-against-the-corona-covid-19-virus.html, has anyone done anything with them? I don't see them as a BOINC listed project. |
|
2)
Message boards :
Number crunching :
The Server Issues / Outages Thread - Panic Mode On! (118)
(Message 2030237)
Posted 1 Feb 2020 by Cliff Harding
Post: There have been a lot of ups and downs lately, but it seems that the downs are winning. So, is this going to be the new normal for the weekends now? |
|
3)
Message boards :
Number crunching :
The Server Issues / Outages Thread - Panic Mode On! (118)
(Message 2028511)
Posted 19 Jan 2020 by Cliff Harding
Post: Please note that I have a test version of a new Lunatics installer, incorporating the new ATI applications. Could testers (only, at this stage, please) PM me for a download link - it could be ideal if anybody with test experience but on your list of card owners could include themselves. How will the new Lunatics version affect NVIDA GPUs, and what else can you tell us about it? Curious minds want to KNOW!! |
|
4)
Message boards :
Number crunching :
The Server Issues / Outages Thread - Panic Mode On! (118)
(Message 2027934)
Posted 16 Jan 2020 by Cliff Harding
Post: I'm now getting this: 01/16/2020 10:22:38 | SETI@home | Reporting 28 completed tasks 01/16/2020 10:22:38 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU 01/16/2020 10:22:38 | SETI@home | [sched_op] CPU work request: 7996094.74 seconds; 0.00 devices 01/16/2020 10:22:38 | SETI@home | [sched_op] NVIDIA GPU work request: 3230248.95 seconds; 0.00 devices 01/16/2020 10:23:59 | | Project communication failed: attempting access to reference site 01/16/2020 10:23:59 | SETI@home | Scheduler request failed: Failure when receiving data from the peer 01/16/2020 10:23:59 | SETI@home | [sched_op] Deferring communication for 00:19:48 01/16/2020 10:23:59 | SETI@home | [sched_op] Reason: Scheduler request failed 01/16/2020 10:24:02 | | Internet access OK - project servers may be temporarily down. I also noticed that it takes up to 20 sec. for a page to load. What other problems do we have? |
|
5)
Message boards :
Number crunching :
The Server Issues / Outages Thread - Panic Mode On! (118)
(Message 2024373)
Posted 22 Dec 2019 by Cliff Harding
Post: I may be an old head, but why doesn't someone back out the changes made that caused this catastrophe in the first place and bounce the servers. Then sandbox the new code until the bug is rectified? At this moment I've 18 hrs (33 CPU tasks) left & 19 tasks that have not been able to report. U/ls have not been a problem. GPUs have been assigned to Milkyway. |
|
6)
Message boards :
Number crunching :
Windows 10 - Yea or Nay? (2)
(Message 2024079)
Posted 21 Dec 2019 by Cliff Harding
Post: Plus the fact that they force you to make a Microsoft account on installation unless you pull out your Ethernet cable disgusted me greatly. In the install process, you can skip that step, it's in fine print (small font) below the account logon. Thus, I've never had to log on the M$S for an install. I do admit that I have to go through some hoops to change the parameters to logon to M$S and back again, that I very rarely us my M$S account. The only thing I'm testing at the moment is the beta version of the new Edge that supposed to come out with the next major release, and I don't need to logon to do it. The only major thing I don't like about is the favorites list. Before the beta version, if you imported your favorites from IE 11 and once you accessed the list it remains visible whenever you hit the favorites button until you exit Edge. Now, under the same scenario, you must hit the favorites button and then the sub-menus (2) until you get the list each and every time you access it. |
|
7)
Message boards :
Number crunching :
The Server Issues / Outages Thread - Panic Mode On! (117)
(Message 2022153)
Posted 7 Dec 2019 by Cliff Harding
Post: I looked at my old log entries and and for me eastern time, it seems to have started at - 06-Dec-2019 23:55:00 [SETI@home] Sending scheduler request: To report completed tasks. 06-Dec-2019 23:55:00 [SETI@home] Reporting 2 completed tasks 06-Dec-2019 23:55:00 [SETI@home] Requesting new tasks for CPU and NVIDIA GPU 06-Dec-2019 23:55:02 [SETI@home] Scheduler request completed: got 66 new tasks |
|
8)
Message boards :
Number crunching :
SETI@Home will now cache 150 CPU work units and 150 per installed GPU
(Message 2022105)
Posted 7 Dec 2019 by Cliff Harding
Post: I thought I was seeing things this morning, but it seems a lot of people are seeing the same thing. I did a quick calculation and it seems that the excess tasks are based on the number of working threads instead of the number of devices. My normal queue is 100/ CPU & 200/ GPU (1 CPU & 2 GPUs). I now have 198 CPU & 793 GPU tasks. That works out to approx. 2 x the number of working threads. Equals out to 4d of CPU & 6d of GPU work. Glad to have it & keep it coming.. |
|
9)
Message boards :
Number crunching :
Machine going south!!
(Message 2010623)
Posted 4 Sep 2019 by Cliff Harding
Post: AT the time of the shutdown, I noticed that the pump was not working and HWinfo64 showed temps in the RED, and did an immediate power off, switch on PSU. Went through 2 more larger pumps purchased locally, Microcenter, which failed with no power. The larger pumps also from EKWB used MOLEX power connectors. Had to go to their web site to find a pump similar to my original and installed it yesterday afternoon. Ran it for several hours without crunching to observe temps. So everything is back up as of 21:30 last night. |
|
10)
Message boards :
Number crunching :
Machine going south!!
(Message 2009467)
Posted 27 Aug 2019 by Cliff Harding
Post: It seems the pump has flailed for my lg. |
|
11)
Message boards :
Number crunching :
Machine going south!!
(Message 2009451)
Posted 27 Aug 2019 by Cliff Harding
Post: Had to power down. Machine over heating from unknown cause(s). May be a couple of days before I'm back up. |
|
12)
Message boards :
Number crunching :
Thermal paste or pad?
(Message 2008964)
Posted 23 Aug 2019 by Cliff Harding
Post: Normally my machine's CPU temps are usually approx. 66-68c (EKWB custom liquid cooling loop) on a consistent basis, even during recent heatwaves where the ambient temps in the room are around 90-95f. The last couple of days machine temps have risen to approx. 78-85c, so I've been thinking of swapping out the thermal paste. Doing some basic research to find a better tim, I ran across thermal pads. Machine temps might increase 2-3c with the pads, and I don't have to be bothered with the mess of cleaning both the CPU and the copper plate of the cooling system, and the pads are reusable. I would like to know if anyone in the Seti-verse have had/are using thermal pads what your thoughts are. |
|
13)
Message boards :
Number crunching :
Welcome to the 20 Year Club!
(Message 2008276)
Posted 19 Aug 2019 by Cliff Harding
Post: WOW Twenty years. Multiple tasks are now done in minutes and I remember when just 1 used to take at least a day and that was just using the CPU. |
|
14)
Message boards :
Number crunching :
Windows 10 - Yea or Nay? (2)
(Message 2007309)
Posted 14 Aug 2019 by Cliff Harding
Post: W7 Pro was set to D/L but ask me before install, a update changed that to auto install and didn't ask permission to change the setting! So I found the box crashed this AM after update Tuesday. Watch out for this sneaky [redacted]. I believe that the same policy lockout also works on W7 Pro. Should have stated this in the initial post, but also noticed that I had to reinstitute the policy after each major upgrade thru 1903. I just put it on the list of things to do after each major upgrade, like changing the TcpWindowSize in the registry, and I still highly recommend it. |
|
15)
Message boards :
Number crunching :
Windows 10 - Yea or Nay? (2)
(Message 2007182)
Posted 13 Aug 2019 by Cliff Harding
Post: Gird yourselves and your systems for these unstoppable Windows updates... ... "there is currently no universal mechanism to keep a Windows machine from loading one of these known bad drivers"... If you have Win10 Pro or Enterprise, after the initial OS install you can prevent auto driver updates via the Group Policy editor. 1) Run Gpedit.msc 2) Navigate to Computer configuration > Administrative templates > Windows components > Windows Update policy 3) On the right side look for Do not include drivers with Windows Update; 4) Open by either double-click or right click and select ENABLE; click OK and exit. Those with the home version have to use regedit and I don't have the details for that. I've used this ever since I noticed that when Windoze updates Nvidia drivers, it doesn't include Open CL, which SETI needs. |
|
16)
Message boards :
Number crunching :
Windows 10 - Yea or Nay? (2)
(Message 2005813)
Posted 5 Aug 2019 by Cliff Harding
Post:
You're right as usual. I was so pi$$$ed that I couldn't even type right. Everything is somewhat back to normal again, but I still have a bunch of applications to install. At least I'm crunching again. |
|
17)
Message boards :
Number crunching :
Windows 10 - Yea or Nay? (2)
(Message 2005618)
Posted 4 Aug 2019 by Cliff Harding
Post: Watch out for the 1609 build. There is a big problem that has shown up tin the last few days. Either of the following will end up in a BLUE SCREEN of DEATH!! 1) If you have either or both a wireless keyboard / mouse the system hangs on the lock screen if the battery is low in either of these. I took me over an hour to find out the problem. 2) If you have an external DVD ( in a caddy) that's connected via USB, beware that the OS may not recognize it if you manually shut it down. I had to use the power strip socket that it was plugged into temporary for another purpose. When I re-attached the DVD everything was normal until I re-cycled the machine and it froze again and went into a sort of Blue Screen of Death. Even a system restore didn't work. The only solution was to do a complete refresh, so I may be sown for a day or 2 while I attempt to reconstruct everything. Apologies to all my wing persons. |
|
18)
Message boards :
Number crunching :
SETI & the system page file?
(Message 2001794)
Posted 9 Jul 2019 by Cliff Harding
Post: Looking at the conversations on this, I decided to change the swap/page file from 'system managed' to a min of 800MB ( btw, is the minimum that windoze allows w/o screaming that if there is a system error that causes a dump, like BSOD, there may not be enough space) and a max of 1000MB. Should be enough for the OS to get by on. |
|
19)
Message boards :
Number crunching :
SETI & the system page file?
(Message 2000472)
Posted 1 Jul 2019 by Cliff Harding
Post: I know I'm showing my age, but if this old man's memory is still largely intact, a great many moons ago there was a discussion on whether or not BOINC, in particular SETI, on using the system page file. In the client computing preferences under the disk & memory tab, there's a box to designate the % of swap/page file that BOINC uses. At the time I think that it was mainly determined that to keep the hammering on the relatively slow ( at that time) HDDs to a minimum and the limited ( compared to todays) storage sizes, that the use of this file be kept to the very minimum (1%). I say 1%, because 0% was not accepted by the client. Fast forward 18 or 19 years and we've come to the age of really fast processors, SSDs, and faster and greater amounts of memory sticks (ram). The question being asked -- Is this thought still viable? Has any further serious thought been given to this in the present days? For example, on my box the system typically allocates approx. 10147mb (system managed), but rarely uses any of it most of the time. I would hate to see all of the space not being utilized. |
|
20)
Message boards :
Number crunching :
User achievements thread.........
(Message 2000030)
Posted 28 Jun 2019 by Cliff Harding
Post: After almost 20 yrs. I cracked 100m tonight, next stop 110m. |
Next 20
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.