Server status page should work again.

BM

First of all, thanks to all who have tested the app so far.

However it seems we could use more testers & feedback, as we see quite a lot of Intel GPU tasks erroring out at Einstein@Home.

I wonder whether this is a driver problem, unfortunately the driver version is not yet recorded on Einstein@Home.

What are the driver versions used here?

Cheers
HB

If someone encounters a driver problem try the following:
https://downloadcenter.intel.com/Default.aspx?ProductFamily=Graphics&ProductLine=Desktop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000%2f2500&ZeroResult=True&lang=eng&ProdId=3498

This is how it should look like:
https://dl.dropboxusercontent.com/u/50246791/Intel%20Driver.PNG
@ select product name one can find his product.
Add a dummy plug, reboot and things should work (did at least twice for me).

Apropos, why are the auto-format buttons like [url] so far off-screen to the right here? I'm using Chrome on Windows XP.

It's the same on IE 10 on Win 7

Claggy

Hi!

There will be a mojor overhaul of the Web presence in the near future, so forgive us for not investing any significant time in fixing stuff in the legacy web front-end now.

Cheers
HB

I notice the Raspberry Pi app has updated to 1.06 now. Were there problems with 1.05 or some further improvements?

<snipped>

I expect no significant performance change.

Cheers
HB

It still hasn't quite finished the 1st one yet (its on 96% after 30 hours). I will provide links once it completes.

OK, next attempt .... I just released version 1.05 for Raspberry Pi . If all goes well this should be 20 - 25 % faster than the previous version.

Feel free to cancel task that are/will be running under version 1.04, this will help to get 1.05 results in soon.

Thanks for testing!!
Cheers
HB

Hi fellow Raspberry Pi fans ;-)


I have released a new test version (1.04) which should be quite a bit faster than the previous one. In general the performance should be somewhere between that of the Android ARMv6 (VFP) 1.03 version and the ARMv7 (NEON) 1.03 version (scaled by clock rate). There were no fundamental changes, just compilation option settings.

<snipped>

Cheers
HB

I've posted some comments in the same thread over at Einstein.

Basically if you switch to https most proxy servers will act as pass thru which means they lose their caching ability. I would suggest only certain bits of the system use https (eg scheduler, website logon) rather than the whole lot.

That is certainly a point to consider, but OTOH, what caching would be affected by this exactly?
For the forum, no caching by the proxy is useful and therefore none should be allowed anyway (you don't want to get a view of the forum as it was minutes ago...it has to be "live"). Also, just having the logon page secured but then later transfer the session credentials (cookies etc) in plain text doesn't help security: it might help against intercepting the password but not against hijacking a session ...

The other big remaining family of web accesses would be downloads. For a single host per proxy, downloading the same file more than once should be a rare thing. But yes, this might be an issue for big "farms" that share one caching proxy. We could indeed exempt those downloads from https.

Cheers
HB

Happy to see what's going on here!
I've set pogs to no new tasks and hope to get one of the arm7 wu's next time a wu is requested.
For now my Nexus (running in Dock, set to use 2 CPU's) crunches a 'single DM'. Now it has reached 32% after 24 hours.

Sounds about right. The NEON version should be almost 4 times faster than this one. Even the ARMv6 version (after the latest update) should be almost twice as fast as the old ARMv6 version you are using now....hopefully.

Cheers
HB

There are an awful lot of Intel CPUs out there with Intel HD graphics. And with the 4000 version used in ivy bridge, it's actually a fairly powerful GPU. Any chance for an opencl app to use this wasted resource?

Sorry for the delay, this one had escaped my attention.

For this to work "out of the box", BOINC has to incorporate support for Intel GPUs as OpenCL capable co-processor.

Also, there have been numerous reports that Intel's OpsnCL drivers prevent other OpenCL drivers (e.g. AMDs) to work with BOINC, so in order to use e,g, Radeon gfx cards for crunching , volunteers had to uninstall the Intel OpenCL drivers. This would have to be solved as well.

Cheers
HB