I HAVE SUSPENDED MY EINSTEIN ACCOUNT UNTIL THINGS ARE PUT RIGHT!
Then I guess you might be suspended for quite a while....
Quote:
How on earth can you expect to have approx 5 hrs of crunch time per week per pc!!!
I really don't understand this point. Are you seriously suggesting that you are unable to have your machine on for just one hour per day???? If so, why are you joining any DC project as it would hardly seem worth your while???
How on earth can you expect to have approx 5 hrs of crunch time per week per pc!!!
Not every project is going to be perfect for all users. It's really up to the project to decide what deadlines are acceptable for their project. I'm sure they would love you to run it, but if you can't make it happen, I'm sure they understand.
Quote:
(running 3Ghz AMD 1GB Ram etc etc)
Really? I wasn't aware there was a 3GHz AMD out yet. Out of curiosity, what CPU is it?
Quote:
I really don't understand this point. Are you seriously suggesting that you are unable to have your machine on for just one hour per day???? If so, why are you joining any DC project as it would hardly seem worth your while???
Indeed not everything will please everyone - however being 'reasonable' pleases most eh? I mean i want to help the project of course, 'help' being the operative word, and the people with PCs that can help is therefore severely restricted due to the very long processing time required for a single project... FYI i run all projects under boinc not just this one, so you see my learned friend approx. 6x 5hrs per week is a long time eh?
Anyhow, why there isnt at least an incremental packet submission as with Climate Predictor is beyond me.
Well theres no need for that is there? To educate the uneducated, even laptops regularly house 3Ghz+ AMDs - if you want to do a search look for Sempron :p
How on earth can you expect to have approx 5 hrs of crunch time per week per pc!!!
Not every project is going to be perfect for all users. It's really up to the project to decide what deadlines are acceptable for their project. I'm sure they would love you to run it, but if you can't make it happen, I'm sure they understand.
Quote:
(running 3Ghz AMD 1GB Ram etc etc)
Really? I wasn't aware there was a 3GHz AMD out yet. Out of curiosity, what CPU is it?
Quote:
I really don't understand this point. Are you seriously suggesting that you are unable to have your machine on for just one hour per day???? If so, why are you joining any DC project as it would hardly seem worth your while???
Indeed not everything will please everyone - however being 'reasonable' pleases most eh? I mean i want to help the project of course, 'help' being the operative word, and the people with PCs that can help is therefore severely restricted due to the very long processing time required for a single project... FYI i run all projects under boinc not just this one, so you see my learned friend approx. 6x 5hrs per week is a long time eh?
Anyhow, why there isnt at least an incremental packet submission as with Climate Predictor is beyond me.
Well theres no need for that is there? To educate the uneducated, even laptops regularly house 3Ghz+ AMDs - if you want to do a search look for Sempron :p
I would suggest that you use a version with the new scheduler. 4.37 and later will enter Earliest Deadline First mode to get the deadline met, and then that project will not get to download work for a while to make up for the extra CPU time needed to get the result in by the deadline.
How on earth can you expect to have approx 5 hrs of crunch time per week per pc!!!
Not every project is going to be perfect for all users. It's really up to the project to decide what deadlines are acceptable for their project. I'm sure they would love you to run it, but if you can't make it happen, I'm sure they understand.
Quote:
(running 3Ghz AMD 1GB Ram etc etc)
Really? I wasn't aware there was a 3GHz AMD out yet. Out of curiosity, what CPU is it?
Quote:
I really don't understand this point. Are you seriously suggesting that you are unable to have your machine on for just one hour per day???? If so, why are you joining any DC project as it would hardly seem worth your while???
Indeed not everything will please everyone - however being 'reasonable' pleases most eh? I mean i want to help the project of course, 'help' being the operative word, and the people with PCs that can help is therefore severely restricted due to the very long processing time required for a single project... FYI i run all projects under boinc not just this one, so you see my learned friend approx. 6x 5hrs per week is a long time eh?
Anyhow, why there isnt at least an incremental packet submission as with Climate Predictor is beyond me.
Well theres no need for that is there? To educate the uneducated, even laptops regularly house 3Ghz+ AMDs - if you want to do a search look for Sempron :p
I would suggest that you use a version with the new scheduler. 4.37 and later will enter Earliest Deadline First mode to get the deadline met, and then that project will not get to download work for a while to make up for the extra CPU time needed to get the result in by the deadline.
FYI i run all projects under boinc not just this one, so you see my learned friend approx. 6x 5hrs per week is a long time eh?
I'm attached to 15 projects and don't have any problems with the deadline...
Quote:
To educate the uneducated, even laptops regularly house 3Ghz+ AMDs - if you want to do a search look for Sempron :p
Hmmm.... OK, a little education back at you...
The numbers given to AMD processors are not the clock speed! The concept is that those numbers are the equivalent clock speed a Pentium would need to run at to have similar performance to the AMD.
The quickest Sempron I can find is the 3300+, which runs at 2GHz. I believe the FX-55 is AMDs highest clocked processor, at 2.6GHz.
For exemple seti@home 2.5hours (deadline 14 days)
einstein 8hours (deadline 7days)
seems reasonable to you ?
Yes it does actually. The project administrators at einstein want work returned sooner than the administrators at SETI. I am sure they have noticed that some people would prefer longer deadlines and have considered it. However they have still come to the conclusion that 7 days is best for the project.
As mentioned previously in this thread update to a client that is more likely to meet the deadlines (4.37+) and give it a rest.
Indeed not everything will please everyone - however being 'reasonable' pleases most eh? I mean i want to help the project of course, 'help' being the operative word, and the people with PCs that can help is therefore severely restricted due to the very long processing time required for a single project
Of course the way E@H sets the deadlines restricts their volunteer community. They understand that, and still set the deadlines that way.
The point is, if you insist on a project doing things your way in order to allow you to offer help, you are a bit like the boy scout who takes the little old lady across the road when she did not want to cross.
E@H have set their deadlines, wu sizes, and so on, as a way of defining what will be helpful to them and what will not be helpful to them.
I am in the same postion with ClimatePrediction - I'd love to be running their project but at present both my machines are slower than their recommended minimum speed. So instead I am offering my machines where they *are* wanted: here till O@H comes online, and then I will try running E@H as my secondary project for a while. If I then start missing E@H deadlines I will drop E@H - but without any bad feeling on my part, nor I am sure on theirs.
You will have to make the same sort of choice. If you want to support E@H you will have to do less on some of your other projects, and the suggestion to use a later BOINC client is a good one because by the time the later clients were written the developers knew about some of E@H's little quirks.
Alternatively, if you don't want to let go of some of your other projects you will have to wave goodbye to gravity ;-)
Your choice, and total respect to you whichever way you choose.
For exemple seti@home 2.5hours (deadline 14 days)
einstein 8hours (deadline 7days)
seems reasonable to you ?
Yes, it seems perfectly reasonable to me. After all we are volunteering (they didn't force us at gunpoint) to help them meet their needs.
We are all calmly and reasonably trying to bring you a message. Please don't shoot the messenger because you don't like the message. Read carefully what JM7 said. That's probably your best approach.
You seem to have convinced yourself that it's impossible to support 5 projects with your AMD 3000+ (I think that's your machine). Actually, I can support both E@H and S@H on a P2 350mHz without going near exceeding a deadline. I could in fact support three projects but two will do nicely. Your machine can support 5 projects with much less than 24/7 operation if you want to. It's up to you. There are many people here who will help you do that if you spell out more fully your requirements and not reply in such an aggressive fashion.
FYI i run all projects under boinc not just this one, so you see my learned friend approx. 6x 5hrs per week is a long time eh?
I'm attached to 15 projects and don't have any problems with the deadline...
Quote:
To educate the uneducated, even laptops regularly house 3Ghz+ AMDs - if you want to do a search look for Sempron :p
Hmmm.... OK, a little education back at you...
The numbers given to AMD processors are not the clock speed! The concept is that those numbers are the equivalent clock speed a Pentium would need to run at to have similar performance to the AMD.
The quickest Sempron I can find is the 3300+, which runs at 2GHz. I believe the FX-55 is AMDs highest clocked processor, at 2.6GHz.
pedanticism is never appealing... GHz is irrelevant as you have shown - the fact is that it takes an average of 5-6hrs per packet - most quote around 30hrs
(p.s. The A64 X2 4800+ is clocked at 2.4GHz - so is that slow?) - sorry if i miss your point :p
and neither is being an obtuse tw*t so i'll shut up now :p
p.p.s. oki oki i got a 3000+ Pentium Rating which actually runs at 2.16 Ghz - happy now :p
RE: I HAVE SUSPENDED MY
)
Then I guess you might be suspended for quite a while....
I really don't understand this point. Are you seriously suggesting that you are unable to have your machine on for just one hour per day???? If so, why are you joining any DC project as it would hardly seem worth your while???
Cheers,
Gary.
RE: RE: How on earth can
)
Indeed not everything will please everyone - however being 'reasonable' pleases most eh? I mean i want to help the project of course, 'help' being the operative word, and the people with PCs that can help is therefore severely restricted due to the very long processing time required for a single project... FYI i run all projects under boinc not just this one, so you see my learned friend approx. 6x 5hrs per week is a long time eh?
Anyhow, why there isnt at least an incremental packet submission as with Climate Predictor is beyond me.
Well theres no need for that is there? To educate the uneducated, even laptops regularly house 3Ghz+ AMDs - if you want to do a search look for Sempron :p
one last point RE: For
)
one last point
seems reasonable to you ?
RE: RE: RE: How on
)
I would suggest that you use a version with the new scheduler. 4.37 and later will enter Earliest Deadline First mode to get the deadline met, and then that project will not get to download work for a while to make up for the extra CPU time needed to get the result in by the deadline.
BOINC WIKI
RE: RE: RE: How on
)
I would suggest that you use a version with the new scheduler. 4.37 and later will enter Earliest Deadline First mode to get the deadline met, and then that project will not get to download work for a while to make up for the extra CPU time needed to get the result in by the deadline.
BOINC WIKI
RE: FYI i run all projects
)
I'm attached to 15 projects and don't have any problems with the deadline...
Hmmm.... OK, a little education back at you...
The numbers given to AMD processors are not the clock speed! The concept is that those numbers are the equivalent clock speed a Pentium would need to run at to have similar performance to the AMD.
The quickest Sempron I can find is the 3300+, which runs at 2GHz. I believe the FX-55 is AMDs highest clocked processor, at 2.6GHz.
RE: one last point
)
Yes it does actually. The project administrators at einstein want work returned sooner than the administrators at SETI. I am sure they have noticed that some people would prefer longer deadlines and have considered it. However they have still come to the conclusion that 7 days is best for the project.
As mentioned previously in this thread update to a client that is more likely to meet the deadlines (4.37+) and give it a rest.
BOINC WIKI
BOINCing since 2002/12/8
RE: Indeed not everything
)
Of course the way E@H sets the deadlines restricts their volunteer community. They understand that, and still set the deadlines that way.
The point is, if you insist on a project doing things your way in order to allow you to offer help, you are a bit like the boy scout who takes the little old lady across the road when she did not want to cross.
E@H have set their deadlines, wu sizes, and so on, as a way of defining what will be helpful to them and what will not be helpful to them.
I am in the same postion with ClimatePrediction - I'd love to be running their project but at present both my machines are slower than their recommended minimum speed. So instead I am offering my machines where they *are* wanted: here till O@H comes online, and then I will try running E@H as my secondary project for a while. If I then start missing E@H deadlines I will drop E@H - but without any bad feeling on my part, nor I am sure on theirs.
You will have to make the same sort of choice. If you want to support E@H you will have to do less on some of your other projects, and the suggestion to use a later BOINC client is a good one because by the time the later clients were written the developers knew about some of E@H's little quirks.
Alternatively, if you don't want to let go of some of your other projects you will have to wave goodbye to gravity ;-)
Your choice, and total respect to you whichever way you choose.
~~gravywavy
RE: one last point
)
Yes, it seems perfectly reasonable to me. After all we are volunteering (they didn't force us at gunpoint) to help them meet their needs.
We are all calmly and reasonably trying to bring you a message. Please don't shoot the messenger because you don't like the message. Read carefully what JM7 said. That's probably your best approach.
You seem to have convinced yourself that it's impossible to support 5 projects with your AMD 3000+ (I think that's your machine). Actually, I can support both E@H and S@H on a P2 350mHz without going near exceeding a deadline. I could in fact support three projects but two will do nicely. Your machine can support 5 projects with much less than 24/7 operation if you want to. It's up to you. There are many people here who will help you do that if you spell out more fully your requirements and not reply in such an aggressive fashion.
Cheers,
Gary.
RE: RE: FYI i run all
)
pedanticism is never appealing... GHz is irrelevant as you have shown - the fact is that it takes an average of 5-6hrs per packet - most quote around 30hrs
(p.s. The A64 X2 4800+ is clocked at 2.4GHz - so is that slow?) - sorry if i miss your point :p
and neither is being an obtuse tw*t so i'll shut up now :p
p.p.s. oki oki i got a 3000+ Pentium Rating which actually runs at 2.16 Ghz - happy now :p