I made the same mistake at Einstein, I had the "minimum work buffer " set to 3 days, as it was for SETI and got 280 GPU tasks with a short deadline, that immediately went into "High Priority" !

When I checked, the advice for people coming from SETI was to set it at 0.5.

They take over an hour and I still have 140 left with a deadline of the 12th, as I am running 2 task on the GPU I should make it.

Team is doing good.

We've come from 6142 rank 2 days ago to 4011 today.

Setizens on Rosetta, come join the team.

---

Dave

Help with rosetta please.
It loads a ton of tasks with a short deadline that stops seti tasks from running. even without seti, it gives me more tasks than I can finish by the deadline.

You are going to need to setup an app_config.xml file in the rosetta project directory with something like this in it.

<app_config>
<project_max_concurrent>4</project_max_concurrent>
</app_config>

Set your defaults on the website or boinc manager to leave at least 1 thread free (75%-90%?).
And keep lowering the max concurrent till Seti starts running again.
You can change the .xml file and then re-read it from the Boinc Manager advanced menu.
Given some time for feedback it will sort out what to send you. The default is 8 hours but it flexs the amount of work it sends you based on the actual speed of your system (based on experience).
You can set the default 8 hours to something else on the website. I wouldn't though.

Tom M

---

A proud member of the OFA (Old Farts Association).

Help with rosetta please.
It loads a ton of tasks with a short deadline that stops seti tasks from running. even without seti, it gives me more tasks than I can finish by the deadline.

Hi Unixchick,

I bet your running the i686 app. I ran into this problem as well. I kept posting that something was wrong either with the app or the tasks and it turns out the i686 app has an issue. The project administrator discovered the problem and suggested to set NNT, which I had done a day or 2 before, until a solution is found.

The tasks have a 4 day deadline and they run on average 8 hours. Another problem is that a checkpoint is not always set and if you log out and back in, some if not all of those tasks will start over at zero %. That is the biggest cause of the high priority run.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Advise, please, most painless way to move BOINCdata folder with projects to another drive.

Easiest way I found is to use symbolic links.

1. Move the entire directory or only certain files and sub-directories to another drive (if you want or need to spread it over multiple disks)

2. Place a symbolic link to the new location(s) at the original location(s)

3. BOINC will operate as if it is still at the original location

If you've never done this: https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

Thanks a lot! Works fine for me. And there is so easy way to do directory junction in Windows with FAR's Alt-F6 commmand!
Will offload part of programs from very small netbook's SSD to microSD card in the same way.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

ooks like they are using Credit New, given the variability of Credit granted. Not as bad as here at Seti (no Anonymous platform support there),

Hehe, only so far :) I already seen questions about Elbrus support via anon platform on their forum, And sources for rosetta mini are available so....

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Team is doing good.

We've come from 6142 rank 2 days ago to 4011 today.

Setizens on Rosetta, come join the team.

Lets beat Rosetta natives/residents with true SETI power! LoL.
(As SETI work finishes I'll add more hosts to fleet to accomplish this goal ;) )

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I give up, and detach that old computer.

I believe World Community Grid has tasks small enough to run in that restricted ram. And they claim they are working on a Coronavid19 project.
PrimeGrid's default 320 Sieve should be able to run also.

Tom

---

A proud member of the OFA (Old Farts Association).

now lots of Rosetta Mini needs 1907.35 MB RAM but only 891.72 MB is available for use

That's odd.
Usually it complains about not enough disk space. The most RAM i've had any Task use is 1.3GB.
Current Rosetta Mini Tasks are using less than 300MB of RAM. Rosetta Tasks are using no more than 750MB (at present).

I had to bump up the disk space for BOINC and the in use/not in use RAM limits to keep Rosetta happy, and turn off HyperThreading on one system (not enough RAM for all the threads). May buy more RAM, we'll see.

---

Grant
Darwin NT

Take a look at your BOINC computation preferences. Uncheck leave CPU tasks in memory when suspended. Also look at the memory use percents. If it is a crunch only box you can safely set them to 100% Frequently these are the issue, as there is room, but not enough to leave a bunch free. Also consider using a config to limit to a single W/U at a time for Rosetta so you don't over commit your RAM.

At the moment I have 5 mini's taking at most 310Mb of RAM/each.

Still looking for as many Setizens as we can get for the Seti orphans team at Rosetta

Let's keep it going.

---

Dave

From 4011 to 3365.

We are making ground

Come join us.

---

Dave

I give up, and detach that old computer.

I believe World Community Grid has tasks small enough to run in that restricted ram. And they claim they are working on a Coronavid19 project.
PrimeGrid's default 320 Sieve should be able to run also.

Tom

Do we have SETI Orphans team there already? If not would be nice to have!

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Take a look at your BOINC computation preferences. Uncheck leave CPU tasks in memory when suspended.

Beware, it can be dangerous! It strongly depends on quality of their checkpointing system and I already read threads on their forums that checkpointing fails sometime. So, all work done will be lost if task ended instead on hold in memory.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Rosetta tasks are strange. Some will grab humungous amounts of memory while others are quite frugal, and the size appears to be set for a batch of tasks.
Another thing to watch out for is their time limits - one can set a limit on the duration of the tasks (I think the figures are1, 3, 6 hours), sometimes the tasks sent will obey the limit (within a couple of minutes), but other times the initial estimate will be OK, but as soon as the task starts the estimate jumps up wildly (1 hour tasks jump to 3, or even 6 hours, and they do take the revised runtime.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Rosetta tasks are strange. Some will grab humungous amounts of memory while others are quite frugal, and the size appears to be set for a batch of tasks.

Yep, i've seen from 112MB up to 1.3GB of RAM required depending on the Task.

Another thing to watch out for is their time limits - one can set a limit on the duration of the tasks (I think the figures are1, 3, 6 hours), sometimes the tasks sent will obey the limit (within a couple of minutes), but other times the initial estimate will be OK, but as soon as the task starts the estimate jumps up wildly (1 hour tasks jump to 3, or even 6 hours, and they do take the revised runtime.

Yeah, I tried all the time limit settings one by one, but that did not make any difference whatsoever.

A changed Target CPU runtime will be applied to Tasks yet to run, those already in progress will keep the Target CPU runtime they started with.
Like Seti, it takes more than just a few returned results for the Estimated completion times to match the actual run times (selectable from 2 hrs to 36, default 8hrs), and given the length of the default (8hrs) it takes a few days for that to happen.

Given that their Tasks run for a set time, it is odd that any newly allocated Tasks don't have that as their Estimated completion time. And as i found out with a batch of dodgy Tasks that errored out instantly- that totally screws up the Estimated completion time for the next Tasks downloaded for that application. Where as here at Seti it was configured to pretty much ignore runtimes of Error or Invalid Tasks and only Valid/Pending/Inconclusive Tasks would impact on Estimated completion times.

---

Grant
Darwin NT

Do we have SETI Orphans team there already? If not would be nice to have!

There is now, just renamed mine. Rosetta too problematic on my systems, so went for WCG. Running it now & when last s@h wu finishes on dual core in 8 hrs, will put that rig on as well.

Will run Rosetta on next rig which should be a Ryzen with more than enough ram. :-)

Will run Rosetta on next rig which should be a Ryzen with more than enough ram. :-)

Allow 1.3GB RAM for each core/thread you plan to have doing work (roughly 300MB HDD space per core/thread), then bump up the allowances in Computing preferences so BOINC can use it and you should be OK.
Oh, and set a really small cache to start with (eg 1 & 0.02).

---

Grant
Darwin NT

Thanks Grant, already aware of that. Sadly this rig is my working machine, Win 7 Pro 32 bit 4gb ram. At most it'll run 2 rosetta with no problems but it is an 8 core both Seti & WCG run 8 while not impacting the rig. :-)

I looked Sten as that was what I wanted, but could only see countries. :-( If anyone knows how to change it to International, I would appreciate it. Thanks.
Just rechecked, couldn't find "International" so left country blank.