I have a theory that since we don't have a linux mb cuda v8 gpu app yet, that's where most of the aps are going to

I have a theory that since we don't have a linux mb cuda v8 gpu app yet, that's where most of the aps are going to

I have been getting afew but I would not say it is more than normal. Nice try though ;).

I have a theory that since we don't have a linux mb cuda v8 gpu app yet, that's where most of the aps are going to

Blaming Linux is as good a reason as any but without data to back it up I would demote it to a hypothesis.

---

I have a theory that since we don't have a linux mb cuda v8 gpu app yet, that's where most of the aps are going to

Blaming Linux is as good a reason as any but without data to back it up I would demote it to a hypothesis.

The 3 linux boxes on the first page of the top hosts list have very few AP. All of the windows boxes seem to have about double the number each linux box does.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

the three linux boxes at the top of the stats are all running anonymous platform so of course they have plenty of v8 mb cuda gpu work

there is no stock v8 mb cuda gpu app for linux so anyone with a linux box with an nvidia gpu would running gpu idle on this project except for v7 resends and aps

but i suppose that my "theories"/thoughts/input isn't good enough so i think i'll just use that as excuse the leave the project

the three linux boxes at the top of the stats are all running anonymous platform so of course they have plenty of v8 mb cuda gpu work

there is no stock v8 mb cuda gpu app for linux so anyone with a linux box with an nvidia gpu would running gpu idle on this project except for v7 resends and aps

but i suppose that my "theories"/thoughts/input isn't good enough so i think i'll just use that as excuse the leave the project

No reason to leave the project....just because you think you are not getting your share of AP tasks???
AP is not the only work available, ya know.
Getting AP work is the luck of the draw.
I have 9 very well running rigs asking for it every time they can, with my preferences set for it as my primary request.
And at present, I have 150 on board...after AP has been splitting for most of the day.
Me whine, hell no.

Everybody wants it, the supply is limited. Catch as catch can, and good luck.

Get over yourself and stay with the project if you admire it's purpose and ideals.

MB is scientifically valid too........

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

It looks like this run is going to wind down 1 box got 46 the other 23, in all not as many as I would have liked.

---

It looks like this run is going to wind down 1 box got 46 the other 23, in all not as many as I would have liked.

I got a mere 20 over two days, that's 10 hours of gpu crunching, till the next batch. Before Xmas, I was getting 50-60 a day, this year has been a struggle.

P.

---

I managed to snag 44 nvidia WUs so far on this run.

---

"Sour Grapes make a bitter Whine." <(0)>

I picked up about 80 on this run, a full boat for my rig. If I could get that weekly, That would be great... ;-)

---

The run looks like it's over 1 box 24 other 51, that's better than nothing but not like it used to be.

---

I picked up about... 3...7. Not a full boat, but that should tide me over for ~4-5 days, depending on how much blanking there is.

I had to baby it the whole time. Set cache to 0.5 days (~130k seconds), and the scheduler finally started giving me one or two every 4 or 5 requests. Once I got a few, I had to increase to 1.0 days, then 2.0, then 4.0, and then I went to bed and just put it back to 10. I guess I got a couple more after that, but not many.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I just saw one of my AP's get massive credit for a wu http://setiathome.berkeley.edu/workunit.php?wuid=2044621862
Im guessing it's because this computer has not done enough AP's (11 validated) yet?
http://setiathome.berkeley.edu/show_host_detail.php?hostid=5541574

---

Just noticed (and aborted, dammit) an AP 7.03 (sse2). I am running stock and specifically set to NO CPU AP. I only process AP on my GPUs.

Is there a new problem with the servers?

---

Remove the section from your app_config. Just a guess, I know that stops getting APs on your CPU.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Just noticed (and aborted, dammit) an AP 7.03 (sse2). I am running stock and specifically set to NO CPU AP. I only process AP on my GPUs.

Is there a new problem with the servers?

I started topic on this issue In regards to switching preferences please have a read in Possibly preferences being ignored? & if you want to share your findings go ahead. People in the know are now aware of the issue.

---

Just noticed (and aborted, dammit) an AP 7.03 (sse2). I am running stock and specifically set to NO CPU AP. I only process AP on my GPUs.

Is there a new problem with the servers?

I started topic on this issue In regards to switching preferences please have a read in Possibly preferences being ignored? & if you want to share your findings go ahead. People in the know are now aware of the issue.

Further info: Just noticed TWO Astropulse v7 7.00 (wu_0, not resends) on my i7-4820K, one of which was running. No CPU type (eg, sse2) was specified. I aborted both.

NOTE: My app_config specifies ONLY max_concurrent (at 3) and gpu_versions for astropulse_v7

My compute prefs specify AP as graphics ONLY.

---

I used to get APs for CPU until I removed AP7_win_x86_SSE3_CPU_r2692.exe and other lines relating to CPU from the app_info.xml created by Lunatics installer

---

Since it seems we are close to getting data from Green Banks does anyone know if APs will be split off that data?

---

I used to get APs for CPU until I removed AP7_win_x86_SSE3_CPU_r2692.exe and other lines relating to CPU from the app_info.xml created by Lunatics installer

An interesting thought, but I am running pure stock now.

And when I was running with Lunatics (before v8) I NEVER saw this problem.

---