http://setiathome.berkeley.edu/result.php?resultid=4973141178

This might be one of them, but no guarantee.I had to use the version you issued to not get stuck.https://setiathome.berkeley.edu/forum_thread.php?id=79629&postid=1793393

I will do a fresh one.

http://setiathome.berkeley.edu/result.php?resultid=4973141178

This might be one of them, but no guarantee.I had to use the version you issued to not get stuck.https://setiathome.berkeley.edu/forum_thread.php?id=79629&postid=1793393

I will do a fresh one.

No errors or restarts for posted result. It just OK with ~52min of elapsed time and ~3min CPU time (not bad too).

EDIT and with -sbs 256 it uses:
Currently allocated 357 MB for GPU buffers

It just OK with ~51min of elapsed time and ~2min CPU time (not bad too).

I am not sure, if it is the one.You still have to remember, that it only finished, because i eventually set it to run by itself.

It just OK with ~51min of elapsed time and ~2min CPU time (not bad too).

I am not sure, if it is the one.You still have to remember, that it only finished, because i eventually set it to run by itself.

Well, try to leave BOINC untouched for awhile. Then if some issue shows up again do new report (with checkable data of course in the report body).

You can always decrease the -sbs to 256 if you want and see if that works better

. . I think with his card 256 might be better, even 384 might be two much for running triples.

Zoom,

Did you also make a app_config.xml and specify 2 work units in it for both SoG and Cuda 42?

Beta2 now available, in both 64-bit and 32-bit versions.

Selected and ran 64bit installer.

Win10 64bit, re-selected CPU AVX application, selected NVidia GPU SoG application (was running CUDA50).
Installed, restarted BOINC.
No problems.
Crunching resumed, cache intact.

. . When you updated to 0.45 I take it your cached WUs remained as CUDA50, is that correct?

Beta2 now available, in both 64-bit and 32-bit versions.

Selected and ran 64bit installer.

Win10 64bit, re-selected CPU AVX application, selected NVidia GPU SoG application (was running CUDA50).
Installed, restarted BOINC.
No problems.
Crunching resumed, cache intact.

. . When you updated to 0.45 I take it your cached WUs remained as CUDA50, is that correct?

Yep.
New work downloaded labelled as SoG.

When I went back to CUDA likewise no issues.
Current work labeled SoG ran OK, all new work labeled as CDUA.

---

Grant
Darwin NT

Ok,

I can't figure out why it's doing the waiting to run part. It should run consecutively. Have you tried decreasing the cache size , maybe it's thinking it won't complete the number of tasks before the deadline?

That is all I can figure for now.

Sorry can't be any more help. I'll keep thinking about it

Z

could it be that the remaining time becomes too long so then boinc decides to move on to the next task that it thinks it can complete before the deadline?

No, I mean how much work do you request in your settings.

Under the preferences it says store at least (blank) days

and additonal (blank) days

I used to use 10 days and 0.1 days for my settings, that filled my cache to 400 work units

However, for you I would think it would try to give you 100 work units

As such, if it thinks it will not complete all those work units in time, it might be switching to the ones closest to timing out and run those.

You could change your preferences to say 0.5 day and 0.1 day and see if that decreases the total amount you get and then see if the work proceeds in order rather than going to the ones with the shortest deadline.

This is just an idea, you don't have to try this if you don't want.

Zoom, things like this I find quite strange,

Restarted at 17.38 percent.
Used GPU device parameters are:
Number of compute units: 16
Single buffer allocation size: 384MB
Total device global memory: 1536MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
LotOfMem path: yes
LowPerformanceGPU path: no
period_iterations_num=50
13:54:12 (55616): Can't acquire lockfile (32) - waiting 35s
13:54:47 (55616): Can't acquire lockfile (32) - exiting
13:54:47 (55616): Error: The process cannot access the file because it is being used by another process.

(0x20)
13:55:44 (43484): BOINC client no longer exists - exiting
13:55:44 (43484): timer handler: client dead, exiting
13:55:54 (43484): BOINC client no longer exists - exiting
13:55:54 (43484): timer handler: client dead, exiting
13:56:03 (53804): Can't acquire lockfile (32) - waiting 35s
13:56:04 (43484): BOINC client no longer exists - exiting
13:56:04 (43484): timer handler: client dead, exiting
13:56:14 (43484): BOINC client no longer exists - exiting
13:56:14 (43484): timer handler: client dead, exiting
13:56:24 (43484): BOINC client no longer exists - exiting
13:56:24 (43484): timer handler: client dead, exiting
13:56:34 (43484): BOINC client no longer exists - exiting
13:56:34 (43484): timer handler: client dead, exiting
13:56:38 (53804): Can't acquire lockfile (32) - exiting
13:56:38 (53804): Error: The process cannot access the file because it is being used by another process.

. . When you updated to 0.45 I take it your cached WUs remained as CUDA50, is that correct?

Yep.
New work downloaded labelled as SoG.

When I went back to CUDA likewise no issues.
Current work labeled SoG ran OK, all new work labeled as CDUA.

. . OK.

. . Mine kept processing but runtimes doubled and I didn't know if that was normal or an issue. So I went back to CUDA50 and like you the return process was seamless but with one exception. When it restored the previous settings it found a version of app_config.xml setup for running doubles, so until the cache is down I will be running twosies :)

. . Then I will reload 0.45 and deal with the tweaking necessary to get it running as smoothly as the 950, well at least as close to it as I can get.

. . The low_performance path options may be a little less co-operative and not so simple to resolve.

[Edit] I only just noticed, because of a message to Zoom, that on the change back the SoG WU's have disappeared. Or at best have been re-identified as CUDA50.

.

Ok,

I can't figure out why it's doing the waiting to run part. It should run consecutively. Have you tried decreasing the cache size , maybe it's thinking it won't complete the number of tasks before the deadline?

That is all I can figure for now.

Sorry can't be any more help. I'll keep thinking about it

Z

No. Is this what you mean by cache? Since the notes for SoG make no mention of cache, yeah I looked.

Disk
Use no more than	100 GB
Leave at least		0.001 GB free
Use no more than	100% of total

. . No he means the WU files cached on your HDD, or as some people call it, your work queue. A little joke there.

. . In BOINC manager, under Options/Computing Preferences/Computing tab, box at the bottom where is says "Store at least xx days of work". Reduce that to a small number to reduce the number of WU files stored in your cache. But it will take time, as the cache only reduces in size as tasks are completed. But it will not replenish until the estimated runtime of remaining WUs is less than the value you have set as above.

. . The part you cited is about disk storage I believe.

I changed that to 10 and 2, the 10 was never higher, the 2 was at 8, that was like that for a long time.

. . I believe 10 is the maximum allowed. But he means a much lower value as he stated of something like 0.5, though you can leave the second line at "0".

. . Just remember it will not reduce immediately.

. . BTW mine is set at 1.5 and zero and is AOK, but I do not have the issues you are talking about.

0.45 has the unfortunate habit of leaving wu's running w/o BoincTasks(1.69), so right now I'm on 0.44. I had 3 files that would cycle, they'd work up to a point, then go back to the last checkpoint, did that several times before I aborted them, since they would just do that over and over all night long if I didn't do something, it's like they had the hiccups.

When 0.44 was installed, SoG went away, so did the 16 Sog wu's which were replaced with 18 guppis, the 16 were also guppis.

. . I think you needed to reset the option in Boinc Tasks to shut down the BOINC client when exiting. They run independently and unless you use that option in Boinc Tasks the BOINC client will continue to run in the background as it is designed to do.

. . There is definitely an issue there with the change back process as when I changed my "little" machine to 0.45 the cache remained intact, no files were lost and the WU process designations remained unchanged. New WUs were labelled SoG. The pre-existing cached CUDA50 files were still CUDA50. But when I changed back the S0G WU's were also gone from BOINC Manager. I cannot tell if the WU files are still in my local cache as there are too many files to manually look at each one to see if it identifies as SoG but the Seti list only shows the files as Anonymous Nvidia GPU not as SoG or CUDA50. Maybe Richard has some insight into that.

The installer is designed to shut down the BOINC client - the bit that runs silently in the background - by itself. If it's running when the installer starts, you should get a warning that it is going to need to do that, and give you the opportunity to cancel.

It doesn't matter to the Installer if BOIMC Manager, BOINC Tasks, or any other user interface is running - nothing the installer does matters to Manager-like tools. In fact, the plan was to leave the Manager running, but close the client and start it back afterwards. If anyone sees anything different to that, please describe with as much detail as you can.

The only change between 0.44 and 0.45 in this area is the detection or 32-bit and 64-bit OSes - I might have broken something there.

Well my slow but sure rise in RAC continues:



Just so you know it is this machine:

6851722

AuthenticAMD
AMD A8-3800 APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
(4 processors)

NVIDIA GeForce GTX 970 (4095MB) driver: 368.22 OpenCL: 1.2

I run two tasks on the 970 and have two CPU cores free.

However it is also my daily machine and I am typing this on it. I watch streaming videos for several hours a day with no noticeable problems. I play games for around 4 hours per day and then Boinc is off.

Just for a historical perspective during last years WOW event this machine peaked at 15,799 RAC, dipped to 3,899 on the 22nd Jan and has not gone higher than 11,458 since.

Before this upturn the lowest point was 6,459. current RAC is 8969

Lets hope it continues.

---

However it is also my daily machine and I am typing this on it. I watch streaming videos for several hours a day with no noticeable problems. I play games for around 4 hours per day and then Boinc is off.

Are you running with the defaults or have to made use of -use sleep?

---

Grant
Darwin NT

I have noticed, that the 64 bit installer shows the warning about boinc running, even if it is not.