Thank you to Matt, Janus and all the others for an excellent week! You put out the fires from last week and deserve our thanks.

---

> Thank you to Matt, Janus and all the others for an excellent week! You put out
> the fires from last week and deserve our thanks.
>
I second that... but...

One last major 'fire' left: Why is Seti Client 4.05 so much slower than 4.03 (or classic for that matter)?????

:^P

> I second that... but...
>
> One last major 'fire' left: Why is Seti Client 4.05 so much slower than 4.03
> (or classic for that matter)?????
>
> :^P
>

Yes the embers are still glowing on that one.

One area that was suggested was the debug code. My personal opinion is that the 4.05 Progress Bar "fix" to make it more linear might be another area to look at.

> One area that was suggested was the debug code. My personal opinion is that
> the 4.05 Progress Bar "fix" to make it more linear might be another area to
> look at.
>
Fixes like THAT we don't need :-(

> One area that was suggested was the debug code. My personal opinion is that
> the 4.05 Progress Bar "fix" to make it more linear might be another area to
> look at.

Could be, but the problem with the bar being non linear was not only due
to the "bar" itself. The SETI application was really crunching harder
during the first part of the WU. Processing itself was non linear.

It has been showed by reading CPU temperature on another thread long ago.

Just a Note for the Admin in case they see this thread:

Do a local test using a test wu with both Seti 4.03 and Seti 4.05 and see what the cpu times are. All the users are betting you will see a large difference.

Keep up the good work. This past week has been a pleasure.

---

> Just a Note for the Admin in case they see this thread:
>
> Do a local test using a test wu with both Seti 4.03 and Seti 4.05 and see what
> the cpu times are. All the users are betting you will see a large difference.
>
> Keep up the good work. This past week has been a pleasure.
>
>
How can the programmers deny what the WU result tables show? All they have to do is look at the CPU times from before everyone updated to Seti 4.05 and compare them to the times from after the 4.05 update. The 50-60 percent increase in times is quite noticable.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.