Having Issues with BOINC not running on my Windows 10 machine
Questions and Answers :
Windows :
Having Issues with BOINC not running on my Windows 10 machine
Message board moderation
| Author | Message |
|---|---|
|
CalicoJack Send message Joined: 9 Sep 02 Posts: 5 Credit: 1,363,903 RAC: 1 
|
Hello, I've noticed lately that most of the time when my laptop (running the current version of Windows 10) is awake and running that it's not running BOINC/seti@home; neither does it go to sleep. it just stays awake all night and does nothing. Sometimes, when I reboot the machine, it will work and run BOINC/seti and process tasks, etc; but mostly not. Further, I was away from home this weekend and connected my laptopn to an unsecure public wifi for a while and surprise surprise it started to work just fine according to my prefs I've begin to wonder if it could be an issue with my home wifi network somehow. Thoughts? Thanks ID: 1977507 ·  |
rob smith    Send message Joined: 7 Mar 03 Posts: 22188 Credit: 416,307,556 RAC: 380 
 |
Since it worked away from home but not at home I'd be looking at your home network Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? ID: 1977517 · |
 Keith Myers  Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
Use the diagnostic flags in the Manager to log extra entries to the Event Log for examination. You are interested in adding the http_debug and the network_status_debug flags to the Event Log diagnostic flags. Should point out what BOINC is having trouble with your home network. Seti@Home classic workunits:20,676 CPU time:74,226 hours   A proud member of the OFA (Old Farts Association) ID: 1977535 · |
|
CalicoJack Send message Joined: 9 Sep 02 Posts: 5 Credit: 1,363,903 RAC: 1
|
OK, having added those two flags, my Event Log now shows me the following: [network status} status: don't need connection It shows me this every second; which is to say it's showing me an ongoing series of such notifications once/second is that of any help? ID: 1977727 · |
|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
With those flags, try clicking the Update button on the Projects tab in the Manager. You should get a lot more output from the flags than "don't need a connection" You should see transactions between the client and the scheduler reporting the status of the connection. Are you sure you selected http_debug? Turn off network_status_debug as it shows you have a connection. You should see something similar to this output for the http_debug flag in the Event Log. Tue 29 Jan 2019 08:19:17 PM PST | | [network_status] status: don't need connection Tue 29 Jan 2019 08:19:18 PM PST | | [network_status] status: don't need connection Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | [sched_op] Starting scheduler request Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | Sending scheduler request: To fetch work. Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | Reporting 11 completed tasks Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | [sched_op] CPU work request: 1123078.75 seconds; 0.00 devices Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | [sched_op] NVIDIA GPU work request: 51744.11 seconds; 0.00 devices Tue 29 Jan 2019 08:19:19 PM PST | SETI@home | [http] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Tue 29 Jan 2019 08:19:19 PM PST | | [network_status] status: online Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Info: Trying 208.68.240.126... Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Info: TCP_NODELAY set Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.126) port 80 (#3014) Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1 Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Host: setiboinc.ssl.berkeley.edu Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.4.44) Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Accept: */* Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Accept-Language: en_US Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Content-Length: 241114 Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Expect: 100-continue Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Sent header to server: Tue 29 Jan 2019 08:19:20 PM PST | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 100 Continue Tue 29 Jan 2019 08:19:21 PM PST | | [network_status] status: online Tue 29 Jan 2019 08:19:21 PM PST | SETI@home | [http] [ID#1] Info: We are completely uploaded and fine Tue 29 Jan 2019 08:19:21 PM PST | | [network_status] status: online Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 200 OK Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: Date: Wed, 30 Jan 2019 04:19:20 GMT Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: Server: Apache/2.2.15 (Scientific Linux) Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: Connection: close Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: Transfer-Encoding: chunked Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/xml Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Received header from server: Tue 29 Jan 2019 08:19:22 PM PST | SETI@home | [http] [ID#1] Info: Closing connection 3014 Tue 29 Jan 2019 08:19:22 PM PST | | [network_status] status: online Tue 29 Jan 2019 08:19:23 PM PST | SETI@home | Scheduler request completed: got 0 new tasks Tue 29 Jan 2019 08:19:23 PM PST | SETI@home | [sched_op] Server version 709 Tue 29 Jan 2019 08:19:23 PM PST | SETI@home | No tasks sent Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) ID: 1977753 · |
|
CalicoJack Send message Joined: 9 Sep 02 Posts: 5 Credit: 1,363,903 RAC: 1
|
Yep, I had http_debug flagged as well. Hit the Update in the Tasks Menu as suggested and got this: 1/30/2019 8:04:11 AM | SETI@home | update requested by user 1/30/2019 8:04:11 AM | | [http] HTTP_OP::init_get(): http://setiathome.berkeley.edu/notices.php?userid=1267552&auth=1267552_88ace1a6da7b9f5f9e6b435235b8c191 1/30/2019 8:04:11 AM | | [http] HTTP_OP::libcurl_exec(): ca-bundle 'C:\Program Files\BOINC\ca-bundle.crt' 1/30/2019 8:04:11 AM | | [http] HTTP_OP::libcurl_exec(): ca-bundle set 1/30/2019 8:04:11 AM | SETI@home | Sending scheduler request: Requested by user. 1/30/2019 8:04:11 AM | SETI@home | Reporting 2 completed tasks 1/30/2019 8:04:11 AM | SETI@home | Not requesting tasks: don't need (CPU: job cache full; NVIDIA GPU: job cache full; Intel GPU: job cache full) 1/30/2019 8:04:11 AM | SETI@home | [http] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 1/30/2019 8:04:11 AM | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle 'C:\Program Files\BOINC\ca-bundle.crt' 1/30/2019 8:04:11 AM | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set 1/30/2019 8:04:12 AM | | [http] [ID#0] Info: Trying 208.68.240.110... 1/30/2019 8:04:12 AM | | [http] [ID#0] Info: Connected to setiathome.berkeley.edu (208.68.240.110) port 80 (#0) 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: GET /notices.php?userid=1267552&auth=1267552_88ace1a6da7b9f5f9e6b435235b8c191 HTTP/1.1 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: Host: setiathome.berkeley.edu 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.14.2) 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: Accept: */* 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: Content-Type: application/x-www-form-urlencoded 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: Accept-Language: en_US 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: 1/30/2019 8:04:12 AM | | [http] [ID#0] Sent header to server: 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Info: Trying 208.68.240.126... 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.126) port 80 (#1) 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Host: setiboinc.ssl.berkeley.edu 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.14.2) 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Accept: */* 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Accept-Language: en_US 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Content-Length: 54781 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: Expect: 100-continue 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: e: en_US 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Sent header to server: 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: HTTP/1.1 200 OK 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: Date: Wed, 30 Jan 2019 13:04:11 GMT 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: Server: Apache/2.2.15 (Scientific Linux) 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: X-Powered-By: PHP/5.3.3 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: Content-Length: 98 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: Connection: close 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: Content-Type: text/html; charset=UTF-8 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: <error> 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: <error_num>-155</error_num> 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: <error_msg>Invalid authenticator</error_msg> 1/30/2019 8:04:12 AM | | [http] [ID#0] Received header from server: </error> 1/30/2019 8:04:12 AM | | [http] [ID#0] Info: Closing connection 0 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 100 Continue 1/30/2019 8:04:12 AM | SETI@home | [http] [ID#1] Info: We are completely uploaded and fine 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 200 OK 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: Date: Wed, 30 Jan 2019 13:04:11 GMT 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: Server: Apache/2.2.15 (Scientific Linux) 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: Connection: close 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: Transfer-Encoding: chunked 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/xml 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: 1547 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <scheduler_reply> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <scheduler_version>709</scheduler_version> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <dont_use_dcf/> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <master_url>http://setiathome.berkeley.edu/</master_url> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <request_delay>303.000000</request_delay> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <project_name>SETI@home</project_name> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <userid>1267552</userid> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <user_name>CalicoJack</user_name> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <user_total_credit>1312218.680374</user_total_credit> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <user_expavg_credit>10.748269</user_expavg_credit> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <user_create_time>1031557718</user_create_time> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <email_hash>2e529db8073aa679d7b40bc0006ba2c3</email_hash> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <cross_project_id>2f803e90ed27496d818ec1739db55eb3</cross_project_id> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <external_cpid>decedc40575630ab443318aee04dc673</external_cpid> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <project_preferences> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <resource_share>100</resource_share> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <no_cpu>0</no_cpu> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <no_ati>0</no_ati> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <no_cuda>0</no_cuda> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <no_intel_gpu>0</no_intel_gpu> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <project_specific> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <format_preset>SETI@home classic</format_preset> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <text_style>Pillars</text_style> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <graph_style>Rectangles</graph_style> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <max_cpu>50</max_cpu> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <grow_time>10</grow_time> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <hold_time>5</hold_time> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <graph_alpha>0.7</graph_alpha> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <roll_period>10</roll_period> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <roll_range>20</roll_range> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <pitch_period>30</pitch_period> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <pitch_range>30</pitch_range> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <starfield_size>2000</starfield_size> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <starfield_speed>40</starfield_speed> 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Received header from server: <color_pre 1/30/2019 8:04:13 AM | SETI@home | [http] [ID#1] Info: Closing connection 1 1/30/2019 8:04:13 AM | SETI@home | Scheduler request completed 1/30/2019 8:04:14 AM | | [http] HTTP_OP::init_get(): http://setiathome.berkeley.edu/notices.php?userid=1267552&auth=1267552_b39977c8c4e9275a37e22d3bcfda4282 1/30/2019 8:04:14 AM | | [http] HTTP_OP::libcurl_exec(): ca-bundle set 1/30/2019 8:04:14 AM | | [http] [ID#0] Info: Hostname setiathome.berkeley.edu was found in DNS cache 1/30/2019 8:04:14 AM | | [http] [ID#0] Info: Trying 208.68.240.110... 1/30/2019 8:04:14 AM | | [http] [ID#0] Info: Connected to setiathome.berkeley.edu (208.68.240.110) port 80 (#2) 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: GET /notices.php?userid=1267552&auth=1267552_b39977c8c4e9275a37e22d3bcfda4282 HTTP/1.1 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: Host: setiathome.berkeley.edu 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.14.2) 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: Accept: */* 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: Content-Type: application/x-www-form-urlencoded 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: Accept-Language: en_US 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: sk questions and report problems</description> 1/30/2019 8:04:14 AM | | [http] [ID#0] Sent header to server: <url>htt 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: HTTP/1.1 200 OK 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Date: Wed, 30 Jan 2019 13:04:13 GMT 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Server: Apache/2.2.15 (Scientific Linux) 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: X-Powered-By: PHP/5.3.3 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Expires: Wed, 30 Jan 2019 13:04:13 GMT 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Last-Modified: Wed, 30 Jan 2019 13:04:13 GMT 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Content-Length: 341 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Connection: close 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: Content-Type: application/xml 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <?xml version="1.0" encoding="ISO-8859-1" ?> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <rss version="2.0"> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <channel> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <title>SETI@home notices</title> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <link>https://setiathome.berkeley.edu/</link> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <description>Notices</description> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: <lastBuildDate>Wed, 30 Jan 2019 13:04:13 GMT</lastBuildDate> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: </channel> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: </rss> 1/30/2019 8:04:14 AM | | [http] [ID#0] Received header from server: 1/30/2019 8:04:14 AM | | [http] [ID#0] Info: Closing connection 2 The two completed tasks I had have gone (so I assume they were uploaded). After hitting the Update button the Status message became Communication Deferred and it gave me a 5:00 count down, after which it did nothing more. During that time, the screen saver didn't come on (it's currently set---to make it easier for testing---at 2 minutes) and no computing started. thoughts? suggestions? (thanks for all the help so far, by the way) ID: 1977792 · |
|
rob smith Send message Joined: 7 Mar 03 Posts: 22188 Credit: 416,307,556 RAC: 380
|
One clue to the lack of action may be in these lines near the start of your log: 1/30/2019 8:04:11 AM | SETI@home | Sending scheduler request: Requested by user. What are your cache settings? From your returned results your appear to be using your Intel GPU as well as an nVidia one and the CPU. Using the Intel GPU is frequently a cause of very poor performance from the CPU, which in turn can hit an nVidia GPU's performance. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? ID: 1977795 · |
|
CalicoJack Send message Joined: 9 Sep 02 Posts: 5 Credit: 1,363,903 RAC: 1
|
How would I look at/change my cache settings? How would I stop using my Intel GPU? I left the machine alone for 2 hours and it didn't process any of the jobs it has on hand. ID: 1977808 · |
|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873
|
I didn't see anything out of the ordinary in the Event Log OTHER than the authenticator error. You change your preferences on the website on your account using the Seti@home Preferences dialog. Turn off use Intel GPU checkmark. You should only have checkmarks on cpu and Nvidia gpu. Go back to the main account page and now open up the Computing Preferences dialog. You want to be using 100% of the cpu and the cpu 100% of the time. Unless you need to use the computer for intensive other work. Go down to the memory section and use 80% of the memory when the computer is in use and 100% of the memory when the computer is not in use. Go to the When to Suspend section and remove any settings there except for the 3 minutes for mouse movement. That is not able to be changed to a blank or 0 setting so don't worry about it. Go to the Other section and set the number of days of work to get. I recommend 1 day of work and 0.1 additional days of work. That will keep your cache filled often and ask for work every 5 minutes. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) ID: 1977816 · |
|
rob smith Send message Joined: 7 Mar 03 Posts: 22188 Credit: 416,307,556 RAC: 380
|
Turning off using the Intel GPU is easiest done from this link: https://setiathome.berkeley.edu/prefs.php?subset=project It may take a couple of hours for changes made here to reach you computer, and any tasks on your computer for the Intel GPU will be run, but no new ones will arrive. Setting your cache can be done from the BOINC GUI: Change to the "advanced" view Then go to "options", and the "computing" tab. At the bottom of that tab you will see two boxes which control the size of your cache: "Store at least xx days of work" and "Store an additional yy days of work". Set xx to something like 6-8 days, and yy to a small number, say 0.1 Now save the changes. Given your results return rate I'm not surprised you didn't see anything happen in two hours, but the "advanced" view will show you how all running tasks are plodding on. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? ID: 1977835 · |
©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.