hi,
and here are my thoughts about the youth:)

Bionic manager 5.10.20 works fine,
but not when it runs on terminal servers..

Specific of some cpu resources in Russia are terminal servers idleness during almost all nights.
But if servers are not completely idling?
And if they are free about 50% any day?
bionic manager is not sufficiently good
in use of these moments.
Can we use this cpu time safely for our tasks?
so I think version 5.10.20 must be optimized,
if you are interested in more cpu power.

best regards..

BOINC tasks run at a low priority, so if the machine has any higher priority work to do, then it will always do that first. The main conflict, if any, will generally be for memory. Sometimes if BOINC has been running a high memory project like Rosetta for a while, it can take some time to bring the memory, needed to run the other work, back from the swap file.

Let me know if I've missed your question.

---

Rosetta Moderator: Mod.Sense

BOINC tasks run at a low priority, so if the machine has any higher priority work to do, then it will always do that first. The main conflict, if any, will generally be for memory. Sometimes if BOINC has been running a high memory project like Rosetta for a while, it can take some time to bring the memory, needed to run the other work, back from the swap file.

Let me know if I've missed your question.

yes,
everything so in the ideal, but in the reality this is the problem.
terminal servers are the server of the interfaces,
and absolutely inadmissibly any influence on their work.
owners can permit using cpu, but they will not suffer the problems.
thanks for the answer

So I believe you are saying that Rosetta continues to run when your Linux box is "in use" by the terminal server.

...this sounds like another flavor of the "Rosetta tasks are not preempting properly on Linux". This is the topic of much discussion here in this thread.

---

Rosetta Moderator: Mod.Sense

So I believe you are saying that Rosetta continues to run when your Linux box is "in use" by the terminal server.

...this sounds like another flavor of the "Rosetta tasks are not preempting properly on Linux". This is the topic of much discussion here in this thread.

you not that understood,

1. terminal server runs on windows server 2003(not linux problem)
2. system already do some other jobs(terminal) in low, and normal priority in the course of the day,

so only advanced task planner can actually completely solve situation like this.
example:
every %x%sec verify the system %idle% value
switch process cpu-usage according user's table

table example:
interval(x)=60,step up=5%,step down=-10%

%idle% >20 -> cpu-usage step up
%idle% <05 -> cpu-usage step down

So I believe you are saying that Rosetta continues to run when your Linux box is "in use" by the terminal server.

Not Linux, i dream cows could fly.. this about "Windows" :)

My mistake, I must have been reading too many Linux threads yesterday :) We're on the Windows board for goodness sake!

ok, so you are saying that the server runs other work that is also at a low priority, and you want to make sure Rosetta doesn't prevent it from running those??

I can tell you are trying to propose a solution here, but I'm having trouble with the language barrier. So, let's first focus on understanding the problem.

Are you actually running Rosetta now on these servers? Or are you trying to first make certain it will not cause you any problems?

You can set the % of CPU you wish to use. For example if you set it to 80% then it will run Rosetta for 4 seconds and then go idle for 1 second (thus giving up the CPU for any other low priority tasks to get work done). On average, you would be within 1.6 seconds of Rosetta going idle or it is idle already.

Or you could mark the other processes as a normal priority, and then they will run if they have work to do, because the CPU runs the highest priority work first, and Rosetta will wait because it has a lower priority. This approach would allow Rosetta to use up to 100% if there is nothing else to do.

To me the second approach sounds better, because what you are really saying is that the other work is a higher priority then Rosetta, but the work is currently not set that way for Windows to understand what to do first.

---

Rosetta Moderator: Mod.Sense

ok, thank's for your time, sorry for my english, i try...
So, let's first focus on understanding the problem.

Are you actually running Rosetta now on these servers? Or are you trying to first make certain it will not cause you any problems?

Yes, I use to run Rossetta at night time on one server of my organization.
Yes, I trying to make certain (about day time).

Is very important to understand several moments:

1. My organization is very typical for Russia, if we about intranet structure.
Terminal server on windows 2003 works with the same program is always present.

2. You say:

To me the second approach sounds better

First Problem is not you, and not me, but owners and people,
who operate this servers. i think you must agree,
that presence of special control options in this programm, will

sounds better(!)

or looks better(!) for anyone else like them.
they are not interested, especially, they don't understand,
and they don't understand, they are cant translate* (forgive me, GOD)

If someone realy want to make excellent programm, what matters?

if your program is not for mac, you loose mac users,
if you dont translate interface, you loose some potential users,
if..if..if
so now, in one of tipical situations, i talk about chances.
your prescriptions are for "clever" people.
I think about *, having the authority to decide.
I know, they can allow something,
if they have levers of the control directly in it.

You could mark the other processes as a normal priority

Yes, it will help me, but it will not solve the problem,
in the week another person will see all of this,
we all have our intrinsic points of view...

Thanks, I could surmise, but
"In the Beginning There WAS THE WORD.." lol :)

By the way, how many cpu power you have from diffrent platforms?
have you statistics?

is it justified to support all of them, or you have any other reasons?
i think the second.

best regards..

If your concern is about hours of the day, you can configure BOINC to only run during your nighttime hours. And not run at all during that day. That would get you started, and if you can find ways to crunch more during the rest of the day that's great, and if not, you are at least running all night.

There are many statistics sites. Here is one by type of host.

---

Rosetta Moderator: Mod.Sense

ok, thank you