11) Message boards : Number crunching : BOINC Supercomputer (Message 46377)
Posted 2637 days ago by Profile God is Love, JC proves it...
Not sure if there might be a better thread for this question, especially as it has been ignored for nearly four weeks, but I concur (mostly):

"My only concern about this project is how long it will be running. Before I put more money to it, I'd like to feel at ease that it won't end any time soon(possibly a time estimate on how long it will run?). Might seem foolish but I see these other projects closing down. I don't want to go out and buy something and then have this project be done."

While I do run quite a few other projects, I (try to) use my GPU exclusively for GpuGrid. (A reasonable alternative was POEM, but that has now folded [pun intended]). I have in the past (about 3-4 years ago) invested in a (+- small) upgrade. I am pondering doing so again. As I've posted before: I am NOT a gamer. I have a GPU solely to support scientific computing projects.

SO, some moderator,... any moderator... any idea how long GPU might keep rolling along?
I presume this really is a question not for a moderator, but for some of the academic faculty doing research which feeds the computing needs for this project.

Thanks,
LLP PhD PE
12) Message boards : Server and website : IS the 5-day (120 hour) time limit enforced on WUs making progress?? (Message 46328)
Posted 2640 days ago by Profile God is Love, JC proves it...
Uncertainty about the timeout being enforced comes from the fact that the Performance page will list several batches with maximum run time (in the box-plots) of well over 120 hours.

In the past couple of weeks, the lion's share of WUs have been running very, very long.
In the past week or so, I have aborted a dozen or more WUs because, while running, they were heading to well over 5 days of compute time.
At this posting I have a WU running with anticipated completion time of just over 11 days (270 hours). I really would like to run this one, since I have not been able to run any GPUGRID WUs in nearly two weeks.

Thanks.
LLP, PhD PE

PS I asked this question on the BNBS thread as part of a post there, but I think the question if pretty important overall for GPUGRID

keywords: Timed out, limit
13) Message boards : Graphics cards (GPUs) : Long runs have too short deadline (Message 46327)
Posted 2640 days ago by Profile God is Love, JC proves it...
First, I'd like to say that I really like supporting GPUGRID as a project. The team publishes results. Also, it seems so many other distributed (grid) computing projects are in theoretical math or in astronomy. I LIKE supporting a project which we can hope will improve human health down the road.

I have a pretty modest GPU (GT 640**) compared to many GPUGRID hosts. However, I have been averaging right at 11 WU a month (almost every single one long-run). Also, I imagine that I am far from unique... that there are many BOINC volunteers 'out there' who have a more modest system (not costing a grand or more, and with no external power supply.)
I appreciate that timely turn-around is important, but there is no other BOINC project of which I am aware with such a short time-out limit on WUs (I am active in 15 projects, not counting several which have by now ended). Ten to 20 days is pretty typically the time limit. SETI has a time limit of over 5 weeks.
So, my question: Is GPUGRID snubbing potential BOINC volunteers who have, say, a GeForce, but not a Titan or whatever?

Thanks.
LLP, PhD PE

** Some 6 years ago, I had a system with a 530. A couple of years later, I upgraded to a 640... I didn't go for more so as to keep my expense to under $100, AND not to have to buy an external power supply.
By the way, I am NOT a gamer at all. I bought the GPU solely to support distributed computing science projects.
14) Message boards : News : WU: BNBS (Message 46326)
Posted 2640 days ago by Profile God is Love, JC proves it...
Greetings;
First, I want to say that I really like supporting GPUGRID as a project. The team publishes results. Also, it seems so many other distributed (grid) computing projects are in theoretical math or in astronomy. I LIKE supporting a project which we can hope will improve human health down the road.
I have a pretty modest GPU (GT 640**) compared to many GPUGRID hosts. However, I have been averaging right at 11 WU a month. Also, I imagine that I am far from unique... that there are many BOINC volunteers 'out there' who have a more modest system (not costing a grand or more, and with no external power supply.)
I appreciate that timely turn-around is important, but there is no other BOINC project of which I am aware with such a short time-out limit on WUs (I am active in 15 projects, not counting several which have by now ended). Ten to 20 days is pretty typically the time limit. SETI has a time limit of over 5 weeks.
So, my First question: Is GPUGRID snubbing potential BOINC volunteers who have, say, a GeForce, but not a Titan or whatever? (This part of the post is perhaps better fitted to another forum.)

In the past couple of weeks, the lion's share of WUs have been BNBS -- and they have been running very, very long.
My second and MAIN question is: is the 5 day timeout enforced on tasks, even if they are making progress?
In the past week or so, I have abort a dozen or more BNBS WUs because, while running, they were heading to 300+ hours of compute time.
At this posting I have a WU running with anticipated completion time of jut over 11 days (270 hours). I really would like to run this one, since I have not been able to run any GPUGRID WUs in nearly two weeks. (In the past POEM was a good backup project, but they have recently terminated.)

My uncertainty about the timeout being enforced comes from the fact that the Performance page will list several batches with maximum run time (in the box-plots) of well over 120 hours.
Thanks.
LLP, PhD PE

** Some 6 years ago, I had a system with a 530. A couple of years later, I upgraded to a 640... I didn't go for more so as to keep a reasonable budget, and not to have to buy an external power source.
By the way, I am NOT a gamer at all. I bought the GPU solely to support distributed computing science projects.
15) Message boards : Number crunching : Scheduler wait: waiting to acquire lock (Message 45802)
Posted 2676 days ago by Profile God is Love, JC proves it...
Yes, deleting the task and getting a new one seems to have worked.
However, the question is STILL unanswered.
John C MacAlister posted this same problem--issue, a couple of years ago... and HE never got a real answer either (not on the boards).

llp

I think ∴ I THINK I am
My thinking neither is the source of my being
NOR proves it to you
God Is Love, Jesus proves it! ∴ we are
16) Message boards : Number crunching : Scheduler wait: waiting to acquire lock (Message 45801)
Posted 2676 days ago by Profile God is Love, JC proves it...
Thanks.

LLP, PhD PE

PS I have deleted the WU, and am trying to get another one (:
So, when I get the next WU I guess for now I just have to keep 'my fingers crossed' that the problem does not recur.

____________
I think ∴ I THINK I am
My thinking neither is the source of my being
NOR proves it to you
God Is Love, Jesus proves it! ∴ we are
17) Message boards : Number crunching : Scheduler wait: waiting to acquire lock (Message 45797)
Posted 2676 days ago by Profile God is Love, JC proves it...
BTW, it is not, I don't believe, a matter of WUs interfering with each other.
Milkyway is using OpenCL.
When I suspend all Milkyway WUs, the same error still keeps coming up for GpuGrid
2016-12-20 4:53:19 PM | GPUGRID | task postponed 600.000000 sec: Waiting to acquire lock

In fact, when I suspend the Milkyway project, the same error still keeps coming up for GpuGrid

Other 'tidbits'
There seems to be no way to restart the task before the 10 min (600.0 sec) has lapsed.
This error always happens right at 30 sec into the task running, and
... each time I suspend other gpu tasks, WT_S3F1_C3-SDOERR_BNBS-0-4-RND3170_1 restarts from 0:00 time elapsed.

llp
18) Message boards : Number crunching : Scheduler wait: waiting to acquire lock (Message 45796)
Posted 2676 days ago by Profile God is Love, JC proves it...
for WU: WT_S3F1_C3-SDOERR_BNBS-0-4-RND3170_1 (http://gpugrid.net/workunit.php?wuid=12213215)

I keep getting a strange error, despite having been running GPU for a couple of years now.
2016-12-20 2:36:15 PM | | Starting BOINC client version 7.6.22 for windows_x86_64
2016-12-20 2:36:15 PM | | log flags: sched_ops, task
2016-12-20 2:36:15 PM | | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
2016-12-20 2:36:15 PM | | Data directory: C:\ProgramData\BOINC\B7 0
2016-12-20 2:36:15 PM | | Running under account Laszlo-Las lo-HPE
2016-12-20 2:36:16 PM | | CUDA: NVIDIA GPU 0: GeForce GT 640 (driver version 376.33, CUDA version 8.0, compute capability 3.5, 1024MB, 834MB available, 803 GFLOPS peak)
2016-12-20 2:36:16 PM | | OpenCL: NVIDIA GPU 0: GeForce GT 640 (driver version 376.33, device version OpenCL 1.2 CUDA, 1024MB, 834MB available, 803 GFLOPS peak)
2016-12-20 2:36:16 PM | | Host name: Laszlo-Laslo-HP
2016-12-20 2:36:16 PM | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz [Family 6 Model 42 Stepping 7]
2016-12-20 2:36:16 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes syscall nx lm avx vmx smx tm2 pbe
2016-12-20 2:36:16 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.14393.00)
2016-12-20 2:36:16 PM | | Memory: 7.98 GB physical, 24.06 GB virtual
2016-12-20 2:36:16 PM | | Disk: 918.83 GB total, 810.22 GB free
2016-12-20 2:36:16 PM | | Local time is UTC -5 hours
2016-12-20 2:36:16 PM | | VirtualBox version: 5.0.12
2016-12-20 2:36:16 PM | | A new version of BOINC is available. (7.6.33) <a href=http://boinc.berkeley.edu/download.php>Download</a>
2016-12-20 2:36:16 PM | GPUGRID | URL http://www.gpugrid.net/; Computer ID 125384; resource share 73
2016-12-20 2:36:16 PM | | General prefs: using separate prefs for home
2016-12-20 2:36:16 PM | | Reading preferences override file
2016-12-20 2:36:16 PM | | Preferences:
2016-12-20 2:36:16 PM | | max memory usage when active: 7193.57MB
2016-12-20 2:36:16 PM | | max memory usage when idle: 7765.79MB
2016-12-20 2:36:16 PM | | max disk usage: 100.00GB
2016-12-20 2:36:16 PM | | suspend work if non-BOINC CPU load exceeds 92%
2016-12-20 2:36:16 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
2016-12-20 2:36:53 PM | GPUGRID | task postponed 600.000000 sec: Waiting to acquire lock

2016-12-20 3:46:14 PM | GPUGRID | task postponed 600.000000 sec: Waiting to acquire lock


...I did just recently update the drivers; however, Milkyway gpu WUs are running just fine.
19) Message boards : Number crunching : All Gerard WUs erroring (Message 42566)
Posted 3025 days ago by Profile God is Love, JC proves it...
WU e15s19_e14s24p1f286-GERARD_CXCL12_DIMPROTO3-0-1-RND3500_2 has been stuck at '85% "progress" ' for some 12 hours now.
I only have a 640, so WUs take 40-60 hours generally.
This task has already run for 69:58.
is this part of a defective batch?
How many more hours should I sacrifice for this WU?
I am presuming that if I abort it, there will be zero credit for these 70 hours (even if it is a flawed WU?)

I Run Win 7 on my HP-1120, i7-2600. (I am NOT going to 'upgrade' to Win 10 for months, until (I hope) MS gets all the garbage in Win8-10 patched up.)

Please advise.

Meanwhile I have paused it and am putting my GPU to better use.

Thanks.
20) Message boards : Multicore CPUs : galaxy s6 (Message 41382)
Posted 3223 days ago by Profile God is Love, JC proves it...
ahhhh when is work scheduled ??

Ditto...


Previous 10 | Next 10
//