It works as explained for me. Give an example were it doesn't control the number of CPUs used by the CPU Applications, or how it controls some other application it's not supposed to. I've tested it extensively, it has absolutely no control over how much CPU the GPU Apps use. The only settings that control how much CPU the GPUs use are application specific controls such as -nobs and -use_sleep. There isn't any BOINC setting that controls how much CPU the GPUs use, but you can set the BOINC CPU control to 100% and starve the GPUs, as the BOINC default setting does.

I have had confusing results. If I set the "app_config.xml" file to 1 cpu per 1 gpu then the "% of cpu cores" to use limits all the cpu threads. If I set the cpu to gpu setting to say 0.33 cpus to 1 gpu then that part of the thread count no longer is constrained. This has predicable results on my cpu usage of pegging to 100%.

I am using -nobs.

I am playing with my % of cpu (threads) parameter. I have changed it from 90% to 95% and picked up some more cpu threads. The task manager is now hovering at about 95% also. It used to be about 90%.

In theory, 4 more cores should increase production, IF the average cpu processing time doesn't go up.

Tom

---

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

This -> Try opening Top and see what you get for setiathome_x41p without any of your kludge settings.
Forgot that part did you?
Listen, I don't care what you do with your machine. What I do care about is this habit a certain 'person' has were he makes it a goal to follow me around and tell people to do exactly the opposite of what I tell them.
I'm sick and tied of it. Now he's trying to convince people there is something wrong with using the same default setting SETI has been using for years.
This is EXACTLY WHY SETI has so few Developers, No One will put up with the type of crap certain users level on the people trying to make SETI work.
If it doesn't stop, there is very dim future ahead.

i did run it, but no amount of proof will sway your opinion.. i dont know why you think -nobs is a "kludge" setting, when you only stopped using it when you started using more GPUs than your CPU could handle while still using -nobs

I had to remove -nobs as well.

here:
app_config.xml removed (i never edited app_info, so it has always had the ncpus setting at 0.1)
-nobs has been removed.
this is stock, default configurations
looks like more than 10% thread use to me




no one is trying to convince anyone of anything except you. we are just saying "this is how it works, and it depends on these settings" and you're saying "no its not! i have different settings and it works differently!"

again it's all about accounting. we prefer to have BOINC properly account for the resources we are using so that the CPU use% setting in the preferences acts in a more intuitive way. setting your CPU use percentage to 1% and having the system still use 60% is counterintuitive.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

This -> Try opening Top and see what you get for setiathome_x41p without any of your kludge settings.
Forgot that part did you?
Listen, I don't care what you do with your machine. What I do care about is this habit a certain 'person' has were he makes it a goal to follow me around and tell people to do exactly the opposite of what I tell them.
I'm sick and tied of it. Now he's trying to convince people there is something wrong with using the same default setting SETI has been using for years.
This is EXACTLY WHY SETI has so few Developers, No One will put up with the type of crap certain users level on the people trying to make SETI work.
If it doesn't stop, there is very dim future ahead.

i did run it, but no amount of proof will sway your opinion.. i dont know why you think -nobs is a "kludge" setting, when you only stopped using it when you started using more GPUs than your CPU could handle while still using -nobs

I had to remove -nobs as well.

here:
app_config.xml removed (i never edited app_info, so it has always had the ncpus setting at 0.1)
-nobs has been removed.
this is stock, default configurations
looks like more than 10% thread use to me




no one is trying to convince anyone of anything except you. we are just saying "this is how it works, and it depends on these settings" and you're saying "no its not! i have different settings and it works differently!"

again it's all about accounting. we prefer to have BOINC properly account for the resources we are using so that the CPU use% setting in the preferences acts in a more intuitive way. setting your CPU use percentage to 1% and having the system still use 60% is counterintuitive.

ONE PERSON has that machine, out of Hundreds of Thousands. Note to the Person that can't understand SETI is for Normal Users.
SETI really doesn't Care about your One machine, try it on a typical machine one of the average of Hundreds of Thousands will be using.
SETI sets the Settings So They Work for the Average user, not the Oddball that keeps trying to tell people to run it his way.

got the same results with my 2x 1080ti system. it's a very normal system. just 2 GPUs plugged directly into a standard ATX motherboard. each x41p app using 30-50% of it's thread.

but i'm sure you've got some other excuse. like i said, this is an act of futility, you've made your mind up that your way is the only way. oh well.

like Keith, petri, Zal, and everyone else running the -nobs "kludge" setting, we don't care if you think it's "wrong". it does what we want and it works how we expect it to.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

This is the Average SETI User;

0.1



You keep mentioning the same handful of people, as if they are somehow suggestive of the average SETI User. NewsFlash, they aren't.

slow, lowend cards like those 750tis require less resources to feed data in and out of them. I don't think that's too surprising.

i already told you that i ran it on a "normal" 2 GPU system that i have, not running any risers or special hardware. and it still uses significantly more than 10% thread use with your non-kludge settings.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Oh, I see. You screwed around with the default settings to get it to do something it wouldn't do with the proper settings.
Why on Earth would I want to do that? The default settings are there for a reason.... they work.

Notice they shut up when I told them to look at Top? Top shows the CUDA App using 0.1 CPU, just as the default settings are set.
That's why there are default settings, set by people that know what they are doing.
I don't care what a handful of fanatics want, I want what will work for the most people using SETI. Maybe that's why I have a handful of Apps on the SETI server, and,
you can count the number of people that have Apps on the SETI server with...well...one hand.

It's called a test to prove that the # CPUs BOINC option affects GPU tasks. And I proved it when some are denying it does nothing for GPUs.

I CLEARLY stated it was a test. I said it. It's in my post, go back and read the whole thing.

TOP is going to show actual CPU usage of which BOINC cannot control. BOINC can only control the # of tasks which % of CPUs affects GPU tasks as well.

Oh, I see. You screwed around with the default settings to get it to do something it wouldn't do with the proper settings.
Why on Earth would I want to do that? The default settings are there for a reason.... they work.

Notice they shut up when I told them to look at Top? Top shows the CUDA App using 0.1 CPU, just as the default settings are set.
That's why there are default settings, set by people that know what they are doing.
I don't care what a handful of fanatics want, I want what will work for the most people using SETI. Maybe that's why I have a handful of Apps on the SETI server, and,
you can count the number of people that have Apps on the SETI server with...well...one hand.

It's called a test to prove that the # CPUs BOINC option affects GPU tasks. And I proved it when some are denying it does nothing for GPUs.

I CLEARLY stated it was a test. I said it. It's in my post, go back and read the whole thing.

TOP is going to show actual CPU usage of which BOINC cannot control. BOINC can only control the # of tasks which % of CPUs affects GPU tasks as well.

That's been known forever. I'm not sure what you are trying to prove. If you set the requirement to 3 CPUs and then Starve the GPU of those 3 CPU resources Of Course the App Won't Run. That's Exactly Why SETI sets the <max_ncpus as low as they Do, so the App won't be starved of the CPU resources and Stop running. What I can't seem to get through to the other person is, it doesn't matter what You think you want to set <max_ncpus to, by changing it higher you change the scheduling and will see unexpected behavior. Such as Apps Not running. That's why you should Leave the <max_ncpus as set by the developers because all you will do by changing it is cause unexpected behavior.

It works as explained for me. Give an example were it doesn't control the number of CPUs used by the CPU Applications, or how it controls some other application it's not supposed to. I've tested it extensively, it has absolutely no control over how much CPU the GPU Apps use. The only settings that control how much CPU the GPUs use are application specific controls such as -nobs and -use_sleep. There isn't any BOINC setting that controls how much CPU the GPUs use, but you can set the BOINC CPU control to 100% and starve the GPUs, as the BOINC default setting does.

I have had confusing results. If I set the "app_config.xml" file to 1 cpu per 1 gpu then the "% of cpu cores" to use limits all the cpu threads. If I set the cpu to gpu setting to say 0.33 cpus to 1 gpu then that part of the thread count no longer is constrained. This has predicable results on my cpu usage of pegging to 100%.

I am using -nobs.

I am playing with my % of cpu (threads) parameter. I have changed it from 90% to 95% and picked up some more cpu threads. The task manager is now hovering at about 95% also. It used to be about 90%.

In theory, 4 more cores should increase production, IF the average cpu processing time doesn't go up.

Tom

I think I remember telling you how to set up the % of CPU the other day. What I don't remember is telling you to change it to 1 cpu per 1 gpu. As soon as you do that you change the scheduling and will see unexpected behavior. You don't have to follow all of what I said about determining how much CPU the GPUs and System use, just change the scheduling back to the defaults, then lower the % CPU use to a point where the CPU isn't Maxed out. That's really all you need to do. Just remember, if the CPU is maxed out it means your GPUs are being starved.

i have not changed the max_ncpus value in the app_info.xml file. i mentioned this is my previous posts.

i doubt Keith or anyone else has either. we use an app_config.xml file with a different parameter.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

i have not changed the max_ncpus value in the app_info.xml file. i mentioned this is my previous posts.

i doubt Keith or anyone else has either. we use an app_config.xml file with a different parameter.

It Makes Absolutely No Difference Where You Change It, the Fact remains you Changed it. You really shouldn't change settings you no nothing about.
With the Default settings I can run 12 GPUs on a 4 core i5 without any trouble, start changing the settings from the defaults and it will choke.

i have not changed the max_ncpus value in the app_info.xml file. i mentioned this is my previous posts.

i doubt Keith or anyone else has either. we use an app_config.xml file with a different parameter.

Correct. I have not touched the app_info default values for max_ncpus. Still at 0.1 for both. The only thing I have done in app_info is change the app over to the CUDA100.
I use app_config's for every project I run. Allows easier setup and tuning without the danger of a typo throwing a cache away.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Remind me again what doesn't work for you. Using the same settings SETI uses I can run 12 GPUs on an i5, My Apps don't Stop, everything works as intended. What can't you get to work this time?

nothing "doesn't work" for me.

It's all working how I want and intend with my settings. that is, a GPU gets 100% of a thread w/ -nobs, and BOINC accounts for that since I told it so in the app_config file.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

nothing "doesn't work" for me.

It's all working how I want and intend with my settings. that is, a GPU gets 100% of a thread w/ -nobs, and BOINC accounts for that since I told it so in the app_config file.

Then what are you going on about? Try running 12 GPUs with an i5 with Your settings and see how it works.
It works perfectly Fine with the settings SETI recommends, I doubt it will with your settings.

We, not just I, are on about your declaration that the CPU% setting in no way affects GPU jobs. And that’s not correct. That is all.

And you’re running them on an i7. Not an i5. Your i7 has8 available threads, an i5 of that gen has only 4

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

This conversation has developed into a personal argument that is not advancing the thread discussion.


I think both side should just agree to disagree.

In some cases it just raises the need to be able to convert seti credits into a Medicare Plan :D

---

The moderating team have reviewed the posts in this thread and some have been removed.

I will open the thread, but if the personal animosity continues the posts will be removed and the thread locked permanently.

Please sort out you personal difficulties privately.

Thank you for understanding.

Don't worry about me. Instead of wasting my time having to respond to the same person every time I post I've decided to just stop posting. Basically, to stop every thing related to SETI except running my machines. SETI won't hear any thing from me for the foreseeable future.
Good Day.