LHC@home

Hello

THis may help someone how is a part of the BOINC test program.

This has only been noticed before I put seti@home on a seperate computer.

A little history

I tried to put LHC on a laptop 550MHz pentium with 84MByte of RAM and Win XP Pro.
As you are probably aware (I was not at time) this was a no goer.
So I resort to removing the SETI@home clasic of the notebook and installed the BOINC SETI@home on the notebook. I then detached the SETI@home project from my main PC. and set up LHC@home on My main machine. I have limited the BOINC client to 2 projects using 1 processor. (I not sure that the result report is correct for this.) But I do know that BOINC is running on one processor and I have folding@home on the other.

But the issue I am refering to I noticed about a day before I moved things around and I know they are not related directly to LHC@home.

the 2 project running on the PC where CPDN resource 100 and SETI resource 100 they both show 50% resource share usage on the project tab, but I noticed that CPDN was being shutdown at about 52-55 minuets processing and SETI was running for about 1hr 15-20mins. (Not really 50/50)

If you set the PC to run only on 1 CPU, it is very likely you saw in the task manager setiathome together with sixtrack if you are using preempting.

Are you sure that at that moment seti was running and not left in memory?


Greetings from Belgium

> If you set the PC to run only on 1 CPU, it is very likely you saw in the task
> manager setiathome together with sixtrack if you are using preempting.
>
> Are you sure that at that moment seti was running and not left in memory?
>
>
> Greetings from Belgium
>
Yes

Sixtrack is not the issue here.
I do not use the option to keep projects in memory.
My system is not I/O Bound it only takes a second or two to switch tha projects.

What has keeping the project in memory got to do with the resources schedulling based on requested parameters.

What version of the Boinc CC do you use? There were some issues concerning the CPU scheduling in version 4.05, but Boinc CC 4.09 fixed (part of) that.

> What version of the Boinc CC do you use? There were some issues concerning the
> CPU scheduling in version 4.05, but Boinc CC 4.09 fixed (part of) that.
>
BOINC 4.09

I have seen this problem now with CPDN and LHC

1 WU completes on LHC 55-59mins and then it immediately switches to CPDN

> > If you set the PC to run only on 1 CPU, it is very likely you saw in the
> task
> > manager setiathome together with sixtrack if you are using preempting.
> >
> > Are you sure that at that moment seti was running and not left in
> memory?
> >
> > [/url]