WinAFC: A new affinity changer

[baobab13]

Now some results:-

C:\FAH\FahCore_*.exe := PAIR0 [assign=2,resource=CPUUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\FAH2\FahCore_*.exe := PAIR1 [assign=2,resource=CPUUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU*\Fahcore_*.exe := ALL [priority=belownormal]

OC, just another note to say that these rules are equivalent to the ones that you used before.

PAIR0 is a shorthand for writing PAIR0::CPU0 + PAIR0::CPU1 (2 CPUs in total).
For the sake of generality let's assume you specify the 'assign' attribute with a value of N and you have M CPUs in the CPU mask.

If N = M, you tell the program to assign all CPUs listed in the CPU mask to all matching processes. In this case the attributes 'resource' and 'policy' are ignored. If N = M, the program does not have to compute resource consumption for matching processes, does not sort the processes by said resource consumption, and does not have to allocate the cores using some fancy policy.
The program just sets the affinity mask of all matching processes to include all CPUs listed in the CPU mask.

So those rules are equivalent to just saying:

C:\FAH\FahCore_*.exe := PAIR0 [priority=idle]						
C:\FAH2\FahCore_*.exe := PAIR1 [priority=idle]						
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU*\Fahcore_*.exe := ALL [priority=belownormal]

Attributes 'resource' and 'policy' are meaningful only when N < M. Note that N cannot be greater than M.

Edit: If you want to test a different config, I would test this one:

C:\FAH\FahCore_*.exe := PAIR0 [assign=1,resource=CPUUSE,policy=PSEUDOBALANCED,priority=idle]
C:\FAH2\FahCore_*.exe := PAIR1 [assign=1,resource=CPUUSE,policy=PSEUDOBALANCED,priority=idle]
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU*\Fahcore_*.exe := PAIR0::CPU1+PAIR1::CPU1 [priority=belownormal]

If your OS is XP and not Vista, then I recommend replacing resource=cpuuse with resource=memuse for both SMP profiles.

[OldChap]

Thanks again, Yes I'm using xp so I will give these a go after work

[OldChap]

Some more results...This time in line with baobab13's recommendations. For me This whole excercise has been a resounding success. Until I finish building another dedicated rig with linux and wine this is the best I could hope for.

My thanks to you baobab13...great piece of work!!

Feel free to ask if you want any other settings tested


C:\FAH\FahCore_*.exe := PAIR0 [assign=1,resource=MEMUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\FAH2\FahCore_*.exe := PAIR1 [assign=1,resource=MEMUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU_card*\Fahcore_*.exe := PAIR0::CPU1+PAIR1::CPU1 [priority=belownormal]
ppd values of wu's.......... gpu2 gpu1 gpu0 smp2 smp1 total
511+480+511+1940+1940 4599 5760 4245 1866 1902 18372
480+384+480+1940+1940 6283 5623 5760 1849 1898 21413
384+384+384+1940+1940 6259 5623 5623 1835 1915 21255
480+384+480+1760+1760 6283 5623 5760 2085 2063 21814
511+384+511+1760+1760 4599 5720 4204 2262 2080 18865

[Marvin_The_Martian]

I do not mind. If you can write a GUI that is intuitive and enables a user to specify all the attributes, that would be very useful.

I am concidering just using it as 3rd party enhanchement for my client installer/manager/monitor which I'm still working on.

The simple and intuitive is hard with the abundant options, and I was hoping getting enough profiles tested by allot of people to just be able to use predetermined profiles based on installed hw, clients and operating system. I got all three of those, I just don't know yet how to generate the best profile for them ( I am following your threads though, and there are more and more cases where it seems a predetermind profile will work ). However if some other affinity changer is used, or the user run software for which it want to create some breating room, that's where it might get tricky.

When I got the basic install validated, and the tray control working fully I'll start on including afc. I done some testings months back but I got permission problems when trying to change affinities, think I know now how to avoid them but it's abit like trying to reinvent the wheel I'd rather use your excellent program and support

[baobab13]

Marvin, that's fine as well. It is an open source project. I guess the GPL license requires only that you make your tool open source as well.

I can also answer questions if you'll have any when you start. I have a few other features that I want to add as well (though a GUI is not on the list ). That's why the program is not at version 1.0 yet.
However, I am a bit more busy now till the end of the year, so these things are on hold.

[Marvin_The_Martian]

Actually I don't have to afaik, I can give users the option to dl your program, and then write profiles for it to read. As I'm not using the sourcecode in my program gpl does not apply?

I'm not against open source, not at all but I spend allot of time on this, and when it's done I want to dedicate it to someone before I will release the sourcecode. I uploaded some much older snippets on google code awhile back, but I think about 60% of the code has been cleaned/improved on so it's not representative of the current state!

[baobab13]

Actually I don't have to afaik, I can give users the option to dl your program, and then write profiles for it to read. As I'm not using the sourcecode in my program gpl does not apply?

I'm not against open source, not at all but I spend allot of time on this, and when it's done I want to dedicate it to someone before I will release the sourcecode. I uploaded some much older snippets on google code awhile back, but I think about 60% of the code has been cleaned/improved on so it's not representative of the current state!

I misunderstood. I thought you wanted to incorporate the code in your program and create/modify profiles dynamically through a GUI. Now I see that you want a GUI to generate the file. Sure, the GPL does not apply in this case.
I am not trying to force open source on you, but in general, when I have a choice I prefer an open source code over a closed one (to download).
Cheers.

[Marvin_The_Martian]

That's true and I want to open source it but I want to finish it before I do. I know my code can be improved upon greatly and I am not doing it for personal glory but I am doing it because I lost people to cancer and this is the only way I could be sure that's rememberd. If I was less afraid of being overlooked, I would opensource it right now, infact I have google code pages where older versions are on, but I haven't put the new config form on it as it's the largest piece of code of the whole program, and also a 100% working way to wrap a gui around the console clients.

Think I just been dissapointed in people to much in the past to have enough trust in the open source community to give me some credit for the time I spend on this

When I get some more confirmation the installer works, that part will be opensourced next week, and I'll work on the tray control for the cllients and the log parsing/qeueu.dat parsing/client control next. I want to include the option to install clients on remote windows computers in the traycontrol, so you can set up a windows farm from a centralized application. I know how to do it, I know it will take some trail and error but I think I can manage it.

I'm all for open source I just want to show something off which works reliable first

[coo-coo-clocker]

Some more results...This time in line with baobab13's recommendations. For me This whole excercise has been a resounding success. Until I finish building another dedicated rig with linux and wine this is the best I could hope for.

My thanks to you baobab13...great piece of work!!

Feel free to ask if you want any other settings tested


C:\FAH\FahCore_*.exe := PAIR0 [assign=1,resource=MEMUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\FAH2\FahCore_*.exe := PAIR1 [assign=1,resource=MEMUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU_card*\Fahcore_*.exe := PAIR0::CPU1+PAIR1::CPU1 [priority=belownormal]
ppd values of wu's......... gpu2 gpu1 gpu0 smp2 smp1 total
511+480+511+1940+1940 4599 5760 4245 1866 1902 18372
480+384+480+1940+1940 6283 5623 5760 1849 1898 21413
384+384+384+1940+1940 6259 5623 5623 1835 1915 21255

Way to go, OC!
Man, you've got that XP rig tweaked very nicely now. And I agree entirely with the kudos for Baobab - it's a nice program - and once we get a few configs that kick ass for different OS/CPU combos, we can deploy quick and easy. Thanks for testing and sharing your results.