2) The source for the special version of CUDA MB is in the svn. This thread is for AP.

You almost certainly correct this thread has got slightly off topic, I would however be interested to know what cards these run on & if I qualify with a 970 can I get a copy to try? I have no idea how to compile code.

I only managed to get a handful of tasks from the latest AP run

---

Other priorities on a long list myself at the moment, but it'll happen all in time :) (That's what it's there for)

So back to the thread topic of AP :)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I have 38 AP's across 4 machines, but I accept any kind of work.

---

The last run did not last very long, a large number of channels just evaporated. Does anybody have an idea what happened?

---

Yeah, I went to bed and there were 170+ channels and then zilch when I woke up. I presume something happened to the splitters.

---

Yeah, I went to bed and there were 170+ channels and then zilch when I woke up. I presume something happened to the splitters.

170 channels only comes to about 75000 AP. Which looks to be about the amount the out in the field went up.

---

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

True, that's just one of the fastest times its burned through that many tapes. It only took it like 6 hours. Normally would have taken twice that long (purely estimating, no imperial data to support that other than my gut and its mainly just hungry right now lol).

---

True, that's just one of the fastest times its burned through that many tapes. It only took it like 6 hours. Normally would have taken twice that long (purely estimating, no imperial data to support that other than my gut and its mainly just hungry right now lol).

Looking at the Haveland graphs it looks about the same as normal to me. Could be the lack of AP in your diet getting to your head :P

---

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

Hal I agree with Chris there were over 200 channels to go when I went to bed last night and they were gone by 4:30 AM PST.

---

True, that's just one of the fastest times its burned through that many tapes. It only took it like 6 hours. Normally would have taken twice that long (purely estimating, no imperial data to support that other than my gut and its mainly just hungry right now lol).

Looking at the Haveland graphs it looks about the same as normal to me. Could be the lack of AP in your diet getting to your head :P

Quite possibly, its the only thing my AMD cards really shine with, so I get grumpy when I don't feel like I get my share lol.

Chris

---

Hal I agree with Chris there were over 200 channels to go when I went to bed last night and they were gone by 4:30 AM PST.

Ah. Possibly only the data sets that have not been processed by AP were actually split. With the remaining channels simply being skipped over.

---

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

I think they evaporate quicker than usual, too, because of idle GPUs since there still isn't a...... what is it, 64-bit Linux CUDA app for MBv8? I know there was one app that hasn't been made yet and apparently it's a fairly popular one, so with a bunch of idle GPUs, once AP splitting happens, they tend to get sucked-up by those idle GPUs faster than usual.

I know I've been having less luck with building a cache the past 10 or so AP runs, but thankfully, I've managed to either get lucky, or chip away at babysitting the cache settings to ask for less than 200,000 seconds of work, and managed to get a reasonable cache for my main cruncher. Depending on blanking, it's about 8 days. Can't really complain.

---

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

I think they evaporate quicker than usual, too, because of idle GPUs since there still isn't a...... what is it, 64-bit Linux CUDA app for MBv8? I know there was one app that hasn't been made yet and apparently it's a fairly popular one, so with a bunch of idle GPUs, once AP splitting happens, they tend to get sucked-up by those idle GPUs faster than usual.

I am not sure you can blame the entire lack of downloaded APs to crunchers who are not yet using a Linux/Nvidia app for V8MBs. I went a month without such an app and I do not think I received any more APs during that period than I did when I was running a V7 app before or a V8 app after - not that it wouldn't have been nice :).

I think they evaporate quicker than usual, too, because of idle GPUs since there still isn't a...... what is it, 64-bit Linux CUDA app for MBv8? I know there was one app that hasn't been made yet and apparently it's a fairly popular one, so with a bunch of idle GPUs, once AP splitting happens, they tend to get sucked-up by those idle GPUs faster than usual.

I am not sure you can blame the entire lack of downloaded APs to crunchers who are not yet using a Linux/Nvidia app for V8MBs. I went a month without such an app and I do not think I received any more APs during that period than I did when I was running a V7 app before or a V8 app after - not that it wouldn't have been nice :).

I think it's slightly more complex than "not getting any more than usual." I think what is mostly driving it is.. when you have all the apps you need for the hardware and environment you're running and your cache is either full (or you're at/near the server-imposed limits), once AP splitting happens, that almost-full cache/limit doesn't allow for very many APs to be grabbed.

But when you've got idle GPUs, and there's a lot of machines that are idle, they may not get very many each, but there are more machines in total that are asking for that type of work, so there's a larger demand than usual, and the same limited supply, so everyone ends up with fewer individually, but overall ("results out in the field") is no different than usual.

---

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

And I think I'm not the only one who's either adding or upgrading capacity. Personally, I've retired all the old XP stuff I was running, but added two quad core Xeons, and about to add a 2xquad core Xeon I just grabbed cheap. With the core2quad, that's 4 boxes, each with 2xGTX750ti. Used to say I was doing this on the cheap ...

---

A few were split today and I got 10 between 2 boxes, all in all not a very satisfying run. There are worse problems in the world but that does disappoint.

---

A few were split today and I got 10 between 2 boxes, all in all not a very satisfying run. There are worse problems in the world but that does disappoint.

I managed 19 between 2. And yes it was not very satisfying....":|

---

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

I managed 19 between 2. And yes it was not very satisfying....":|

Got 23 for the new cruncher so far, counting what's splitting now, at least enough to know it's not gonna implode. 112 total, I think. No idea how I got that lucky ...

---

Looking at the Haveland graphs it looks about the same as normal to me. Could be the lack of AP in your diet getting to your head :P

Very interesting page, didn't know it existed. It seems that the S@H part is for v7 only... is there a page for v8 somewhere?
(sorry for the off topic)

Looking at the Haveland graphs it looks about the same as normal to me. Could be the lack of AP in your diet getting to your head :P

Very interesting page, didn't know it existed. It seems that the S@H part is for v7 only... is there a page for v8 somewhere?
(sorry for the off topic)

I don't think so. I would guess they are reading the first two columns under Database/file status from the Server status. I believe the same thing occurred in transition from Astropulse v6 to v7.
As the three apps being displayed is only temporary the person running the stats site probably doesn't see the need to do more coding. I don't think I would myself. I'm happy they have taken the time to publish the info.

---

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