It took quite a while to 'catch up' the deficiency. (how do I get the box that you use for quotes?)
I can answer this part on how I do it...see up top at the very beginning when you click Quote to reply to a message the very first thing is a {with the word quote then an equals sign and my name and then another }? That's who a quote box starts, you can leave off the name if you want too but I leave it on the first time and then off the rest of the times unless I'm quoting multiple people in one post. At the end of a quote you need to close the box and you do that by putting another one { and then a / and then the word quote and then a }. You can see this at the very last line of my reply as it's the end.
So if I wanted to quote you I would copy the
schildbuerger wrote:
along with your words and then at the end I would put
This is what I do. It's what I'm doing in this reply.
Right click the 'quote' link (top line of message you're responding to) and select "open in a new tab" so the reply is in a separate browser tab from the original thread.
In the new tab, you will see the opening tag (including the poster's name) at the start and the closing tag at the very end, all inside a text composition box.
In my opinion it's quite lazy to leave a longish message if you're only responding to a particular sentence so select and remove those portions that are irrelevant to your reply. If somebody wants to read the full original message they can go to the original without having to suffer a full copy of the whole thing being shoved in their face once again :-).
If you are responding to multiple sentences from the original message, just leave those sentences and copy the original opening quote tag and paste that in front of each additional sentence. Also insert a closing quote tag (type it in or paste a copy) at the end of each additional sentence. That way it's very clear as to what you're responding to and what you're response exactly is.
If you get stuck on how to do something, make sure you expand the drop-down BBCODE HELP menu item that's always found below the text composition box you are using to compose your message. There's lots of useful stuff in there. There are 2 lines about quote tags quite close to the bottom of the multiple pages of BBCODE instructions.
schildbuerger wrote:
... So we can configure BOINC as it will be best for its demands but uses only one core. What settings would you suggest in concrete?
Exactly what I've already suggested.
Leave the setting for % of cores BOINC is allowed to use at 50%.
Make sure you tick the setting for "Leave tasks in memory when suspended".
Remove the restriction that would cause BOINC to suspend if CPU use exceeds 25%.
Make sure you scroll to the bottom and click "Save" when finished.
You can also click "Update" in BOINC Manager to force the client to contact the server immediately to become aware of the changes you have made.
I would be very surprised if you could notice any effect of these changes on the performance of your main job. If you do and if these effects are unacceptable, then perhaps you should consider not using BOINC on that machine.
schildbuerger wrote:
How do I update to a new BOINC version? My Linux knowledges are quite low so I would need a concrete command. In the seti forum I found ....
What's not 'concrete' about that set of commands? :-).
As I understand it (google his name for yourself) Gianfranco Costamagna is a Debian developer of some repute. Ubuntu is a Debian derivative. I also think he may be involved in BOINC development at some level. Without doing any research, I would tend to think that what he suggests would be the correct way to upgrade your BOINC installation. Having said that and as I mentioned earlier, there should be nothing wrong with your current version 7.2.42. For your very straight forward use case, you could easily leave it where it is. I'm still running 7.2.42 on a number of machines and there doesn't seem to be much problem with that.
schildbuerger wrote:
And on BOINC Forum there is a completely different process for that task.
Do you believe everything you read on the internet? ;-) :-). A number of things are immediately obvious.
The post was made in 2010. A lot of things change in 9 years.
He has a total of 3 posts in all that time.
His very next post was an "Oops" in response to the first one.
He is a user with no apparent affiliation with the BOINC Devs.
He is obviously unhappy with the way that Ubuntu creates a separate user:group of boinc:boinc under which BOINC runs. That way is OK for the 'set and forget' people who don't want to fiddle but quite annoying and frustrating for the tinkerers who don't have a good grasp of Unix/Linux file ownership and user and group permissions. Even though I do have sufficient understanding to handle all that, I would still find it incredibly frustrating if I had to do things the "Ubuntu way". :-).
What he has produced is a mishmash of the original Berkeley shell archive installer as modified to (sort of) cope with how Ubuntu needs to have things done. If you had a good understanding of Linux, you could get something to work along those lines. From your comment about your Linux knowledge, you should be very wary about trying to follow this.
schildbuerger wrote:
The current einstein task is the only one in the tasklist, it shows 64,672% progress, 9:03h done and 2:21h remaining.
Those figures point to a finish of the primary calculations (~90%) in a total of just over 12.5hrs as compared to 11.5hrs that was indicated earlier. In my experience, a total predicted at the ~30% complete stage is usually reasonably accurate so I think that after your app finished recording, maybe it did some heavier CPU use work that took some CPU time away from the science app. If (when the task is finished and returned) you look on the website and see a big difference between the CPU time and the elapsed time (say more than an hour) you could suspect that this was going on at some point after the 30% stage probably.
I hadn't seen this message when I posted my previous one.
On the website, the RUN time and CPU time are reasonably close - a difference only 10mins so no real indication that the science app was being held up by any competing process. For the moment, everything looks good.
The Changes on the preferences (from your earlier post) are implemented and I can do a rollback if something surprising will happen, but I also do not expect that.
Coming weekend I will try the apt-get commands from seti-forum to update BOINC, after I read the post up to the end. Thanks for your vote for it! I preferred them also, but in the past I've destroyed my installation when I tried to install nvidea drivers to support GPU on the installed video card, so I'm a bit careful before I take hands on the system :-)
Everybody sees a small difference between CPU time and Elapsed (RUN) time. This is quite normal. There should be no concern about the current amount of that difference. If it grew to be say 10-20% of the total time, it would be an indication that the machine is struggling to cope with the workload. If the non-BOINC workload is high, so be it. BOINC is designed to get out of the way.
The only thing you need to check occasionally is that the one task doesn't get into a state where it never makes real progress. Maybe every couple of days have a quick look to make sure it's not the same task still running with no sign of significant progress.
schildbuerger wrote:Hi
)
Hello MIKEY, thanks for the
)
Hello MIKEY,
thanks for the hint, but it doesn't work with {} it needs [] to do the job. With that and no spaces around the equal sign it looks like this:
Regards,
Klaus
Hello Gery, here is an
)
Hello Gery,
here is an update from the task. It is done quite now, upload has finished and I got two new milkyway tasks.
Regards,
Klaus
schildbuerger wrote:... how
)
This is what I do. It's what I'm doing in this reply.
Exactly what I've already suggested.
I would be very surprised if you could notice any effect of these changes on the performance of your main job. If you do and if these effects are unacceptable, then perhaps you should consider not using BOINC on that machine.
What's not 'concrete' about that set of commands? :-).
As I understand it (google his name for yourself) Gianfranco Costamagna is a Debian developer of some repute. Ubuntu is a Debian derivative. I also think he may be involved in BOINC development at some level. Without doing any research, I would tend to think that what he suggests would be the correct way to upgrade your BOINC installation. Having said that and as I mentioned earlier, there should be nothing wrong with your current version 7.2.42. For your very straight forward use case, you could easily leave it where it is. I'm still running 7.2.42 on a number of machines and there doesn't seem to be much problem with that.
Do you believe everything you read on the internet? ;-) :-). A number of things are immediately obvious.
Those figures point to a finish of the primary calculations (~90%) in a total of just over 12.5hrs as compared to 11.5hrs that was indicated earlier. In my experience, a total predicted at the ~30% complete stage is usually reasonably accurate so I think that after your app finished recording, maybe it did some heavier CPU use work that took some CPU time away from the science app. If (when the task is finished and returned) you look on the website and see a big difference between the CPU time and the elapsed time (say more than an hour) you could suspect that this was going on at some point after the 30% stage probably.
Cheers,
Gary.
schildbuerger wrote:... It is
)
I hadn't seen this message when I posted my previous one.
On the website, the RUN time and CPU time are reasonably close - a difference only 10mins so no real indication that the science app was being held up by any competing process. For the moment, everything looks good.
Cheers,
Gary.
schildbuerger wrote:Hello
)
You are right!!! Sorry about that!!!
Hi Gery, Gary Roberts
)
Hi Gery,
I agree to this.
The Changes on the preferences (from your earlier post) are implemented and I can do a rollback if something surprising will happen, but I also do not expect that.
Coming weekend I will try the apt-get commands from seti-forum to update BOINC, after I read the post up to the end. Thanks for your vote for it! I preferred them also, but in the past I've destroyed my installation when I tried to install nvidea drivers to support GPU on the installed video card, so I'm a bit careful before I take hands on the system :-)
Regards,
Klaus
Hi Together, here comes a
)
Hi Together,
here comes a short update. The computer has made it's next einstein task.
In total the last task has finished a lot faster but the difference between run- and cpt-time has not significant changed.
@Gery: Did the changes have worked as expected?
Greetings,
Klaus
schildbuerger wrote:... Did
)
Yes, everything continues to look as it should.
Everybody sees a small difference between CPU time and Elapsed (RUN) time. This is quite normal. There should be no concern about the current amount of that difference. If it grew to be say 10-20% of the total time, it would be an indication that the machine is struggling to cope with the workload. If the non-BOINC workload is high, so be it. BOINC is designed to get out of the way.
The only thing you need to check occasionally is that the one task doesn't get into a state where it never makes real progress. Maybe every couple of days have a quick look to make sure it's not the same task still running with no sign of significant progress.
Cheers,
Gary.
Hi Gary, from my point of
)
Hi Gary,
from my point of view every thing looks fine too.
I will take care of it in the futere,
Thanks a lot,
Klaus