. . HI People

. . This is off topic but I am not sure where to ask this question.

. . On the Seti HQ site when I look up "My Computers" to see how they are going, the data is wrong and has not changed in about 24 hours. Has anyone else noticed this problem and is there anything to be done to correct it?

Stephen

.

. . HI People

. . This is off topic but I am not sure where to ask this question.

. . On the Seti HQ site when I look up "My Computers" to see how they are going, the data is wrong and has not changed in about 24 hours. Has anyone else noticed this problem and is there anything to be done to correct it?

Stephen

.

You dont need to ask the same question in different threads.

Replica database is offline so nothing special.

---

With each crime and every kindness we birth our future.

. . This is off topic but I am not sure where to ask this question.

Such questions in "Panic Mode On (###) Server Problems?"
Last posts in it talk about this:
http://setiathome.berkeley.edu/forum_thread.php?id=79575&postid=1822079#1822079

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

In case it helps ...

(1) I just aborted a opencl_ati5_cat132 task; it got stuck at 87.554%. I noticed at 1:37 elapsed (0:13:51 remaining). About five minutes later, same percentage, but 1:42 elapsed and 0:14:33 remaining). Good news: no problems with latency.

(2) I'm experimenting with the "-period_iterations_num" setting in the BOINC/projects/setathome.berkeley.edu/mb_cmdline-8.12_windows_intel__opencl*.txt files. Below the low number, my computer is not responsive enough while I'm working. Above the high number, responsiveness is fine. With each new task, I'm narrowing the range. Here are interim results.
opencl_ati_cat132: 100 to 960
opencl_ati5_cat132: 1500 to 3000
opencl_ati5_SoG_cat132: 2220 to 3000
opencl_atiapu_sah: 2000 was bad, on next task I'll use 3000, looking for an upper bound
opencl_atiapu_SoG: 3000 was good, on next task I'll use 1900

(3) My system logs indicate there have been no display driver freezes since before 9/28 (which is welcome!)

Not all the tasks lag the same - VLAR lag most, VHAR least

The new apps r3500+ have much less lag

No need to wait for "each new task" - just check/uncheck 'Snooze GPU' after you change the cmdline

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Not all the tasks lag the same - VLAR lag most, VHAR least

The new apps r3500+ have much less lag

No need to wait for "each new task" - just check/uncheck 'Snooze GPU' after you change the cmdline

. . Again, worth knowing, is that the same as selecting "Options"/"Read config file" ??

. . I am always curious if there is a difference, because the second option does not seem to take immediate effect.

Stephen

.

"is that the same" - which "that"?
'Snooze GPU' is from the BOINC Manager icon in systray

"if there is a difference" - between?
"the second option" - which is it?
'Snooze GPU' is not "Read config file"

"Read config file" - Read again cc_config.xml & app_config.xml

As you can see from the page on cc_config.xml :
"If you edit the file while BOINC is running, the changes will take effect only if you select the Advanced / Read config file menu item. (Note: some changes in the <options> section take effect only when you restart the BOINC client)."

(Quote only the part which you will comment to avoid confusion)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

'Read config files' is designed to modify the way BOINC works. It has no direct effect on the science applications.

Modified command lines take effect when the science applications start up, only. 'Snooze GPU' stops the GPU science applications, and unsnoozing GPUs allows them to start up again, reading the new command lines in the process.

'Read config files' is designed to modify the way BOINC works. It has no direct effect on the science applications.

Modified command lines take effect when the science applications start up, only. 'Snooze GPU' stops the GPU science applications, and unsnoozing GPUs allows them to start up again, reading the new command lines in the process.

. . Thanks for the clarification Richard, succinctly put.

Stephen

.

v8.19 released so this thread came to its end. New one will be started.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.