I have a 100Mhz MIPS Linux/SGI machine that ought to be able to do some amount of work. Unfortunately, it doesn't seem to complete in the two-week deadline. Is the machine simply too slow? Or is something wrong with my compiled version?
Host ID 389414.

---

Depends on the actual System.

I have a few running for me (SGI Irix 6.5.x, BOINC V4.59, SETI V4.03), the slowest ones roughly yielding these numbers :

SGI Power Indigo2 R8000 75MHz (2MB L2) : 49 hours
SGI Indy R5000 180MHz (512k L2) : 44-45 hours
SGI Indigo2 R4400 250MHz (2MB L2) : 39 hours

Yours seems a Version with PC (Primary Cache) only, therfor it will indeed take a longer time.
But IMHO it should still finish within the 2 weeks limit (based on my experience with a R5000-150PC versus the R5000-180SC, the lack of L2 Cache approximately doubles the runtime).

The way I see it, your compiled Clients (especially the SETI Core Client) might need some optimization.
Since I don't know how well the Linux Port for MIPS Clients performs in comparison to SGI Irix 6.5, that's my best educated guess (maybe need to tinker with optimization switches).

Otherwise, you can only check for other Services or Applications taking away CPU time. IMHO, the R4000-100PC should easily manage 2 weeks return time, I would expect something like 7-9 days completion time from that machine.

If you can afford it, I would try to aquire a faster CPU with Secondary Cache, the lack of SC is otherwise a significant performance toll that can be avoided for very little money (EBay frequently has extremely cheap sales of older MIPS CPUs). Many Indigo2's can go upto R4400-250MHz (2MB L2), all of them should be able to take an R4400-200MHz (1MB L2).

---