Here's a link to a E@H participant's CPU that is a perfect example of why I think the deadlines should be shorter, not longer. What’s the deal with this?
> Here's a link to a E@H participant's CPU that is a perfect example of why I
> think the deadlines should be shorter, not longer. What’s the deal
> with this?
>
> Case
> study for shorter deadlines!
>
>
>
>
hm... thats a single case... i dont want to say that they have to be longer, but i think 1 week is the minimum to make it possible for everyone to participate...
> Here's a link to a E@H participant's CPU that is a perfect example of why I
> think the deadlines should be shorter, not longer. What’s the deal
> with this?
>
> Case
> study for shorter deadlines!
>
Or a perfect example of why the scheduler should be notified by the client then it detaches/resets the project.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
Ziran wrote:
> Since you have HT enabled on your machine you will always have at lest 2
> Einstein WU’s on your machine if you don’t participate in multiple
> projects. The “connect to� setting will only influence how long in advance
> you will download an additional WU.
This is the default setting, i.e. 2 WUs with HT.
But you can change it that way :
- Account
-- view or edit general preferences
--- edit preferences
---- On multiprocessors, use at most ... processors
----- type 1
... and you'll have only one WU running, still with HT.
I joined Einstein@home yesterday. I was surprised to see the quantity of work downloaded to my machine. When I did the sums, I realised that with my existing preferences, not all of the the E@H WU's would complete before the deadline. So I have now adjusted the preferences to accommodate.
Once these WU are flushed out, I should then be able to re-adjust to something more balanced.
Projects: Seti, CPDN and now E@H
Machine: 3.0Ghz P4 (HT) running 24/7
Old connect settings :4 days
Old Resource share : equal share to each project
New connect settings :1 day
New Resource share : Seti 10% (server issues), CPDN 1% (12 months to complete a WU) and E@H 89%.
My point is that I consider myself to be reasonably well educated on running Boinc and it still caught me out. I'm no expert, but I think a large number of new E@H recruits may not spot the risk of the short reporting deadline.
I think the real fix for this is not to increase the deadlines, but as others have suggested to get the CC to take account of project loading and resource share before downloading work that can't be completed in time.
Nonetheless, I'm proud to be involved in E@H and wish everybody happy crunching.
> My point is that I consider myself to be reasonably well educated on running
> Boinc and it still caught me out. I'm no expert, but I think a large number
> of new E@H recruits may not spot the risk of the short reporting deadline.
I'm running multiple projects since some 5 months. Quite honestly, I think I understand quite fairly how to deal with resource share and setting a fairly good "connect to" number. Nevertheless, with E@H I got for the first time problem passing deadline.
> I think the real fix for this is not to increase the deadlines, but as others
> have suggested to get the CC to take account of project loading and resource
> share before downloading work that can't be completed in time.
One thing I still don't understand comparing E@H with S@H and LHC@Home is why E@H downloads big files that remains on your PC and containing a lot of WU's itself. Why not using a method like S@H and LHC@Home where each WU is downloaded one by one. This gives a more flexible way to deal with the deadline and to addapt more easely the WU's Boinc is downloading.
One thing that has become apparent to me is that people in general, at least the people that post here, set their caches to high. I don't know if it is motivated by a paranoia about not being able to connect and get more work or if it is just an over sensitivity to being out of work for a few minutes while their machines connect and get work but I for one want the absolute minimum of work units sitting on my hard drives and I have never had a problem of having no work.
I think the default of 0.1 days to connect to the network is ideal if you have a connection that is always on. If you're crunching 24x7 then maybe 0.5 - 1 days. If you're dial up, then that is another matter entirely and maybe most people are on dial up connections.
There have been a very few instances where one of the 4 projects I'm working on couldn't provide me work but that's why there's BOINC in the first place, so you can work on multiple projects so this is a non-issue. One project has no work, BOINC just rolls to the next in line. On my machines, all projects share equally, it makes it so simple, why make it complicated.
> One thing I still don't understand comparing E@H with S@H and LHC@Home is why
> E@H downloads big files that remains on your PC and containing a lot of WU's
> itself. Why not using a method like S@H and LHC@Home where each WU is
> downloaded one by one.
As far as I know, some of the Einstein 'work unit' you download is re used each time you get a new work unit. The scheduler determines what type of unit you have already downloaded and then sends you similar type work keeping your overall download size to a minimum but requiring a slightly bigger hard disk footprint that would otherwise be expected...
maybe I'm totally wrong on that but I seem to remember reading a post along those lines before...
> As far as I know, some of the Einstein 'work unit' you download is re used
> each time you get a new work unit. The scheduler determines what type of unit
> you have already downloaded and then sends you similar type work keeping your
> overall download size to a minimum but requiring a slightly bigger hard disk
> footprint that would otherwise be expected...
>
> maybe I'm totally wrong on that but I seem to remember reading a post along
> those lines before...
What I can see on my PC, with an orginal setting of "connect to" at 2 days, is I have a file "H1_0306.4" that has been downloaded the 11th and another file "H1_0416.4" that has been downloaded the 14th.
Any WU that I'm still crunching is still coming for those 2 files and no other files have been downloaded since the 14th.
> What I can see on my PC, with an orginal setting of "connect to" at 2 days, is
> I have a file "H1_0306.4" that has been downloaded the 11th and another file
> "H1_0416.4" that has been downloaded the 14th.
> Any WU that I'm still crunching is still coming for those 2 files and no other
> files have been downloaded since the 14th.
>
I have something similar myself. I don't pretend to know the exact details behind it but I can see from my logs that I have uploaded and downloaded several workunits today from the server. What I can see is that, like you, I can see two 'work units' in the project folder. They are H1_0367.9 and H1_0344.4. All of the WUs I have uploaded and downloaded today start with these 'IDs' (actually they are all H1_0344.4__**)....
Perhaps someone with a more detailed knowledge is reading these posts and can explain it to us?
[EDIT] This is the thread I was thinking of when I wrote my previous message... (just found it!)
[/Edit]
Here's a link to a E@H
)
Here's a link to a E@H participant's CPU that is a perfect example of why I think the deadlines should be shorter, not longer. What’s the deal with this?
Case study for shorter deadlines!
There's a fine line between fishing and standing on the shore looking like an idiot -- Steven Wright
> Here's a link to a E@H
)
> Here's a link to a E@H participant's CPU that is a perfect example of why I
> think the deadlines should be shorter, not longer. What’s the deal
> with this?
>
> Case
> study for shorter deadlines!
>
>
>
>
hm... thats a single case... i dont want to say that they have to be longer, but i think 1 week is the minimum to make it possible for everyone to participate...
> Here's a link to a E@H
)
> Here's a link to a E@H participant's CPU that is a perfect example of why I
> think the deadlines should be shorter, not longer. What’s the deal
> with this?
>
> Case
> study for shorter deadlines!
>
Or a perfect example of why the scheduler should be notified by the client then it detaches/resets the project.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
Ziran wrote: > Since you
)
Ziran wrote:
> Since you have HT enabled on your machine you will always have at lest 2
> Einstein WU’s on your machine if you don’t participate in multiple
> projects. The “connect to� setting will only influence how long in advance
> you will download an additional WU.
This is the default setting, i.e. 2 WUs with HT.
But you can change it that way :
- Account
-- view or edit general preferences
--- edit preferences
---- On multiprocessors, use at most ... processors
----- type 1
... and you'll have only one WU running, still with HT.
JF.
Hi Guys, I joined
)
Hi Guys,
I joined Einstein@home yesterday. I was surprised to see the quantity of work downloaded to my machine. When I did the sums, I realised that with my existing preferences, not all of the the E@H WU's would complete before the deadline. So I have now adjusted the preferences to accommodate.
Once these WU are flushed out, I should then be able to re-adjust to something more balanced.
Projects: Seti, CPDN and now E@H
Machine: 3.0Ghz P4 (HT) running 24/7
Old connect settings :4 days
Old Resource share : equal share to each project
New connect settings :1 day
New Resource share : Seti 10% (server issues), CPDN 1% (12 months to complete a WU) and E@H 89%.
My point is that I consider myself to be reasonably well educated on running Boinc and it still caught me out. I'm no expert, but I think a large number of new E@H recruits may not spot the risk of the short reporting deadline.
I think the real fix for this is not to increase the deadlines, but as others have suggested to get the CC to take account of project loading and resource share before downloading work that can't be completed in time.
Nonetheless, I'm proud to be involved in E@H and wish everybody happy crunching.
Richard
> My point is that I consider
)
> My point is that I consider myself to be reasonably well educated on running
> Boinc and it still caught me out. I'm no expert, but I think a large number
> of new E@H recruits may not spot the risk of the short reporting deadline.
I'm running multiple projects since some 5 months. Quite honestly, I think I understand quite fairly how to deal with resource share and setting a fairly good "connect to" number. Nevertheless, with E@H I got for the first time problem passing deadline.
> I think the real fix for this is not to increase the deadlines, but as others
> have suggested to get the CC to take account of project loading and resource
> share before downloading work that can't be completed in time.
One thing I still don't understand comparing E@H with S@H and LHC@Home is why E@H downloads big files that remains on your PC and containing a lot of WU's itself. Why not using a method like S@H and LHC@Home where each WU is downloaded one by one. This gives a more flexible way to deal with the deadline and to addapt more easely the WU's Boinc is downloading.
Greetings from Belgium
Thierry
One thing that has become
)
One thing that has become apparent to me is that people in general, at least the people that post here, set their caches to high. I don't know if it is motivated by a paranoia about not being able to connect and get more work or if it is just an over sensitivity to being out of work for a few minutes while their machines connect and get work but I for one want the absolute minimum of work units sitting on my hard drives and I have never had a problem of having no work.
I think the default of 0.1 days to connect to the network is ideal if you have a connection that is always on. If you're crunching 24x7 then maybe 0.5 - 1 days. If you're dial up, then that is another matter entirely and maybe most people are on dial up connections.
There have been a very few instances where one of the 4 projects I'm working on couldn't provide me work but that's why there's BOINC in the first place, so you can work on multiple projects so this is a non-issue. One project has no work, BOINC just rolls to the next in line. On my machines, all projects share equally, it makes it so simple, why make it complicated.
> One thing I still don't
)
> One thing I still don't understand comparing E@H with S@H and LHC@Home is why
> E@H downloads big files that remains on your PC and containing a lot of WU's
> itself. Why not using a method like S@H and LHC@Home where each WU is
> downloaded one by one.
As far as I know, some of the Einstein 'work unit' you download is re used each time you get a new work unit. The scheduler determines what type of unit you have already downloaded and then sends you similar type work keeping your overall download size to a minimum but requiring a slightly bigger hard disk footprint that would otherwise be expected...
maybe I'm totally wrong on that but I seem to remember reading a post along those lines before...
Wanna visit BOINC Synergy site? Click my stats!
Join BOINC Synergy Team
> As far as I know, some of
)
> As far as I know, some of the Einstein 'work unit' you download is re used
> each time you get a new work unit. The scheduler determines what type of unit
> you have already downloaded and then sends you similar type work keeping your
> overall download size to a minimum but requiring a slightly bigger hard disk
> footprint that would otherwise be expected...
>
> maybe I'm totally wrong on that but I seem to remember reading a post along
> those lines before...
What I can see on my PC, with an orginal setting of "connect to" at 2 days, is I have a file "H1_0306.4" that has been downloaded the 11th and another file "H1_0416.4" that has been downloaded the 14th.
Any WU that I'm still crunching is still coming for those 2 files and no other files have been downloaded since the 14th.
Greetings from Belgium
Thierry
> What I can see on my PC,
)
> What I can see on my PC, with an orginal setting of "connect to" at 2 days, is
> I have a file "H1_0306.4" that has been downloaded the 11th and another file
> "H1_0416.4" that has been downloaded the 14th.
> Any WU that I'm still crunching is still coming for those 2 files and no other
> files have been downloaded since the 14th.
>
I have something similar myself. I don't pretend to know the exact details behind it but I can see from my logs that I have uploaded and downloaded several workunits today from the server. What I can see is that, like you, I can see two 'work units' in the project folder. They are H1_0367.9 and H1_0344.4. All of the WUs I have uploaded and downloaded today start with these 'IDs' (actually they are all H1_0344.4__**)....
Perhaps someone with a more detailed knowledge is reading these posts and can explain it to us?
[EDIT]
This is the thread I was thinking of when I wrote my previous message... (just found it!)
[/Edit]
Wanna visit BOINC Synergy site? Click my stats!
Join BOINC Synergy Team