>>The Core Client doesn't actually do any of the work. It won't affect the speed of the E@H project application.
Not so.
The core client is responsible for handling some of the interface between the science app and the system - it has to be, since it manages communications, prioritisation, disk I/O and a number of other things. Variations in Core Client will affect the overall performance of the science app to a greater or lesser extent.
There was much anguish over this issue on the SETI boards when an earlier version of the core client was released and slowed everyone up. I wish I could find the threads. Maybe someone else can help.
> >>The Core Client doesn't actually do any of the work. It won't affect
> the speed of the E@H project application.
>
> Not so.
>
> The core client is responsible for handling some of the interface between the
> science app and the system - it has to be, since it manages communications,
> prioritisation, disk I/O and a number of other things. Variations in Core
> Client will affect the overall performance of the science app to a greater or
> lesser extent.
The difference is small enough as to be irrelevent. Definitely not 20-30 minutes...
> There was much anguish over this issue on the SETI boards when an earlier
> version of the core client was released and slowed everyone up. I wish I could
> find the threads. Maybe someone else can help.
4.16 a little bit slowly
)
The Core Client doesn't actually do any of the work. It won't affect the speed of the E@H project application.
I suspect what you are seeing is simple WU variation.
>>The Core Client doesn't
)
>>The Core Client doesn't actually do any of the work. It won't affect the speed of the E@H project application.
Not so.
The core client is responsible for handling some of the interface between the science app and the system - it has to be, since it manages communications, prioritisation, disk I/O and a number of other things. Variations in Core Client will affect the overall performance of the science app to a greater or lesser extent.
There was much anguish over this issue on the SETI boards when an earlier version of the core client was released and slowed everyone up. I wish I could find the threads. Maybe someone else can help.
It may take longer but you
)
It may take longer but you claim more credits also, so it evens out in the end ... IMO
> >>The Core Client doesn't
)
> >>The Core Client doesn't actually do any of the work. It won't affect
> the speed of the E@H project application.
>
> Not so.
>
> The core client is responsible for handling some of the interface between the
> science app and the system - it has to be, since it manages communications,
> prioritisation, disk I/O and a number of other things. Variations in Core
> Client will affect the overall performance of the science app to a greater or
> lesser extent.
The difference is small enough as to be irrelevent. Definitely not 20-30 minutes...
> There was much anguish over this issue on the SETI boards when an earlier
> version of the core client was released and slowed everyone up. I wish I could
> find the threads. Maybe someone else can help.
No, that was a project .exe. 4.05 I believe.