// DBOINCP-300: added node comment count condition in order to get Preview working ?>
richardthomas21
Joined: 9 Feb 05
Posts: 3
Credit: 1110
RAC: 0
27 Feb 2005 4:07:43 UTC
Topic 188075
(moderation:
)
checked my computer on the E@H site, and it has me listed @ 2048 MBs of RAM, when in actuality, I have 4,096 megs. How does E@H deyermine the RAM on one's computer?
> checked my computer on the E@H site, and it has me listed @ 2048 MBs of RAM,
> when in actuality, I have 4,096 megs. How does E@H deyermine the RAM on one's
> computer?
It's actually the core client and not the worker application (E@H) that determines the amount of memory on a system.
A bug has been filed, hopefully somebody can look in to it and get it fixed. In reality, it shouldn't cause any problems for you.
> > checked my computer on the E@H site, and it has me listed @ 2048 MBs of
> RAM,
> > when in actuality, I have 4,096 megs. How does E@H deyermine the RAM on
> one's
> > computer?
>
> It's actually the core client and not the worker application (E@H) that
> determines the amount of memory on a system.
>
> A bug has been filed, hopefully somebody can look in to it and get it fixed.
> In reality, it shouldn't cause any problems for you.
>
Thanks, Rob, appreciate your response, though I'm not sure I understand the concept of "core client" relative to memory; I understand core clients relative to CPU cycles because I can see the effect in my Activity Monitor: three Folding clients running in two cores and one Einstein per core (one of the Folding clients is hyperthreaded, hence the reason for the odd number).
> > > checked my computer on the E@H site, and it has me listed @ 2048 MBs
> of
> > RAM,
> > > when in actuality, I have 4,096 megs. How does E@H deyermine the RAM
> on
> > one's
> > > computer?
> >
> > It's actually the core client and not the worker application (E@H) that
> > determines the amount of memory on a system.
> >
> > A bug has been filed, hopefully somebody can look in to it and get it
> fixed.
> > In reality, it shouldn't cause any problems for you.
> >
>
> Thanks, Rob, appreciate your response, though I'm not sure I understand the
> concept of "core client" relative to memory; I understand core clients
> relative to CPU cycles because I can see the effect in my Activity Monitor:
> three Folding clients running in two cores and one Einstein per core (one of
> the Folding clients is hyperthreaded, hence the reason for the odd number).
>
Oops ... for got to add that all five clients use +/- 35% of CPU when all 5 are active.
> Thanks, Rob, appreciate your response, though I'm not sure I understand the
> concept of "core client" relative to memory; I understand core clients
> relative to CPU cycles because I can see the effect in my Activity Monitor:
> three Folding clients running in two cores and one Einstein per core (one of
> the Folding clients is hyperthreaded, hence the reason for the odd number).
The 'Core Client' is Boinc, the main program/GUI you run your scientific applications on, like Einstein, Seti, ClimatePrediction, LHC, ProteinPredictor...
AFAIK Folding doesn't use Boinc, so it's competing with Boinc for your system. Perhaps that's the reason (or part of it).
The Folding equivalent in Boinc is ProteinPredictor (again: afaik)
> It doesn't - neither does the core client. The core client simply reports what
> the system tells it.
That might account for the weirdness I am seeing on a machine that dual boots Windows XP and Fedora Core 3. The Computer Number assigned to the Windows install shows the appropriate 512 MB RAM and under linux the client reports only 503 MB.
Memory reported in error
)
> checked my computer on the E@H site, and it has me listed @ 2048 MBs of RAM,
> when in actuality, I have 4,096 megs. How does E@H deyermine the RAM on one's
> computer?
It's actually the core client and not the worker application (E@H) that determines the amount of memory on a system.
A bug has been filed, hopefully somebody can look in to it and get it fixed. In reality, it shouldn't cause any problems for you.
Rob
> > checked my computer on
)
> > checked my computer on the E@H site, and it has me listed @ 2048 MBs of
> RAM,
> > when in actuality, I have 4,096 megs. How does E@H deyermine the RAM on
> one's
> > computer?
>
> It's actually the core client and not the worker application (E@H) that
> determines the amount of memory on a system.
>
> A bug has been filed, hopefully somebody can look in to it and get it fixed.
> In reality, it shouldn't cause any problems for you.
>
Thanks, Rob, appreciate your response, though I'm not sure I understand the concept of "core client" relative to memory; I understand core clients relative to CPU cycles because I can see the effect in my Activity Monitor: three Folding clients running in two cores and one Einstein per core (one of the Folding clients is hyperthreaded, hence the reason for the odd number).
> > > checked my computer on
)
> > > checked my computer on the E@H site, and it has me listed @ 2048 MBs
> of
> > RAM,
> > > when in actuality, I have 4,096 megs. How does E@H deyermine the RAM
> on
> > one's
> > > computer?
> >
> > It's actually the core client and not the worker application (E@H) that
> > determines the amount of memory on a system.
> >
> > A bug has been filed, hopefully somebody can look in to it and get it
> fixed.
> > In reality, it shouldn't cause any problems for you.
> >
>
> Thanks, Rob, appreciate your response, though I'm not sure I understand the
> concept of "core client" relative to memory; I understand core clients
> relative to CPU cycles because I can see the effect in my Activity Monitor:
> three Folding clients running in two cores and one Einstein per core (one of
> the Folding clients is hyperthreaded, hence the reason for the odd number).
>
Oops ... for got to add that all five clients use +/- 35% of CPU when all 5 are active.
> Thanks, Rob, appreciate
)
> Thanks, Rob, appreciate your response, though I'm not sure I understand the
> concept of "core client" relative to memory; I understand core clients
> relative to CPU cycles because I can see the effect in my Activity Monitor:
> three Folding clients running in two cores and one Einstein per core (one of
> the Folding clients is hyperthreaded, hence the reason for the odd number).
The 'Core Client' is Boinc, the main program/GUI you run your scientific applications on, like Einstein, Seti, ClimatePrediction, LHC, ProteinPredictor...
AFAIK Folding doesn't use Boinc, so it's competing with Boinc for your system. Perhaps that's the reason (or part of it).
The Folding equivalent in Boinc is ProteinPredictor (again: afaik)
Grüße vom Sänger
> checked my computer on the
)
> checked my computer on the E@H site, and it has me listed @ 2048 MBs of RAM,
That's probably correct.
> when in actuality, I have 4,096 megs.
2048 MB per CPU?
> How does E@H deyermine the RAM on one's computer?
It doesn't - neither does the core client. The core client simply reports what the system tells it.
Be lucky,
Neil
> It doesn't - neither does
)
> It doesn't - neither does the core client. The core client simply reports what
> the system tells it.
That might account for the weirdness I am seeing on a machine that dual boots Windows XP and Fedora Core 3. The Computer Number assigned to the Windows install shows the appropriate 512 MB RAM and under linux the client reports only 503 MB.