I've noticed that some WUs are getting low credits, is there a problem somewhere? It's not happening only with the latest app, it also happened with previous versions, not sure when I first noticed it.

I've noticed that some WUs are getting low credits, is there a problem somewhere? It's not happening only with the latest app, it also happened with previous versions, not sure when I first noticed it.

No there's some that only gives around 150-250 and not around 600-800 as normal. Right now there's only one with 140.64 Cr on my finished WUs list, last when I wrote there was 3-4 WUs with the low credit.

Well, DownLoads are very slow at SETI, comaired to projects with
fewer users and hosts, GPUgrid hits 20MBit, Einstein is also faster.
Milkyway, WCG, etc..
Problem is SETI is constant overloaded/saturated and in too much cases
the cause of a DownLoad Errors as in your case.

I've noticed that some WUs are getting low credits, is there a problem somewhere? It's not happening only with the latest app, it also happened with previous versions, not sure when I first noticed it.

No there's some that only gives around 150-250 and not around 600-800 as normal. Right now there's only one with 140.64 Cr on my finished WUs list, last when I wrote there was 3-4 WUs with the low credit.

Well, DownLoads are very slow at SETI, comaired to projects with
fewer users and hosts, GPUgrid hits 20MBit, Einstein is also faster.
Milkyway, WCG, etc..
Problem is SETI is constant overloaded/saturated and in too much cases
the cause of a DownLoad Errors as in your case.

How long for a MB (~360KBytes) and AstroPulse (8MBytes) workunit?

FFor astro: more than 3 hours in download time but I have caused to manually restart the download dozens of times

Just some more feedback for Raistmer and any other AP OpenCL developers:

Getting a lot of invalid results on my old HD 4670, mostly due to 30 single pulses, 30 repeating pulses, or both. This seems to happen regardless of what combination of parameters I try. The confusing thing is that, sporadically, I still get the occasional valid result.

I think I'll have to revert to r555 even though it has much lower performance (especially with regards to CPU usage), it's still bound to be much better than CPU-only processing on the ancient machine it's on. There were still invalid results, but they were limited to 30 repeating pulses and there were far more valid results than invalid ones. I put all this down to the 'beta-level' OpenCL support on the HD 4000 series - I ceased all GPU processing on my HD 4850 a long time ago because of similar issues presumably arising from this.

Other GPUs (HD 5000 series and later, as well as GeForce cards) continue to work very well on r1316. I'm aware there is a r1363 release, but I don't understand the parameters enough to try it. Doesn't seem as though there's as large a performance increase either.
____________
Soli Deo Gloria

Yes. As I mentioned, the both valid and invalid results occur for all manner of parameters. I've tried unroll of 4, 8, 10 with r1316. With r555, unroll of 4 always resulted in invalid results, whereas 10 was the only one that consistently returned valid results.
____________
Soli Deo Gloria

Just some more feedback for Raistmer and any other AP OpenCL developers:

Getting a lot of invalid results on my old HD 4670, mostly due to 30 single pulses, 30 repeating pulses, or both. This seems to happen regardless of what combination of parameters I try. The confusing thing is that, sporadically, I still get the occasional valid result.

I think I'll have to revert to r555 even though it has much lower performance (especially with regards to CPU usage), it's still bound to be much better than CPU-only processing on the ancient machine it's on. There were still invalid results, but they were limited to 30 repeating pulses and there were far more valid results than invalid ones. I put all this down to the 'beta-level' OpenCL support on the HD 4000 series - I ceased all GPU processing on my HD 4850 a long time ago because of similar issues presumably arising from this.

Other GPUs (HD 5000 series and later, as well as GeForce cards) continue to work very well on r1316. I'm aware there is a r1363 release, but I don't understand the parameters enough to try it. Doesn't seem as though there's as large a performance increase either.

Actually I'm trying to maintain compatibility with HD4xxx though has no hardware installed now. But HD46xx low-end ones AFAIK and have some different issues.
Special LHD4 build for them still in debugging. From the other side I would not expect same failures on HD4850. Can you replace HD46xx with HD48xx on that host ?

As mentioned previously, the puzzling thing is that there are still some valid results produced with r1316. These two were validated recently, so they're still present in the database at time of writing:

Oops, no, scratch that. Second one just got purged as I was writing...

Edit: If you want a tester for your special HD 4000 build, I'm willing to help. Will just take a while as 0% blanking AP WUs take about 7.5 hours with r1316, just under 10 hours with r555.
____________
Soli Deo Gloria