Why are deadlines so *short*?

We currently don't have any plans to change the deadlines, neither with current, nor with future Apps.

With the switch to S5R3 we got a variation in runtime that we didn't expect. We are working on the workunit generator to adjust the credits given accordingly, it might be a good idea to dynamically extend the deadline a few days for longer running results, too. But it will stay in the same order (two to three weeks).

One reason for testing the SSE(2) code on MacOS is that all Intel Macs have CPUs with the same features (SSE, SSE2 etc.). I have various issues with this code on other platforms that are not solved yet, some depend on the compiler used, some require certain CPU features, requiring feature detection, maintenance of different code paths etc. It's actually all a lot easier on Intel Macs. And yes, the stability issues of the other platforms are the bigger concern for us.

A cross-project credit comparison can be seen here. According to this Einstein@Home is currently granting more credits per CPU hour than most other projects (the numbers in the Einstein@Home row are mostly >= 1.0), though a bit less than SETI.

BM