Fidelizer 2.0 - Introducing new UI with multi-core optimizations

[lag0a]

Using Fidelizer 1.6, Extremist mode, Unchecked Keep Network services and User experience but my internet still works so isn't it suppose to be shutdown since I didn't check Network services? Anyone's internet still work with Network services unchecked?

 

[WindowsX]

Version 2.0 is out. Now it comes with multi-core processor resource assignment optimizations and fixed audiophile player running at lowest priority issue.


Changes in version 2.0
-Added processor core resource assignment for multi-core optimizations
-Fixed process priority optimizations so that new process like audiophile player won't start with lowest priority
-Redesigned UI with selectable features list controlled by optimization level
 

 

[Waqar]

Wow just amazing, great work an of course thank you for this great tweak.
 

 

[JavierS]

I'm getting clicks/pops whenever I do anything, like opening the browser or even a new tab in it. I'm using the latest version 2 in custom mode and stopping everything except networking, it happens with both PCI and USB sound cards. In 1.6 using Extremist and just keeping networking this didn't happen, is there any kind of bug?
Cheers

 

[svyr]

Version 2.0 is out. Now it comes with multi-core processor resource assignment optimizations and fixed audiophile player running at lowest priority issue.


Changes in version 2.0
-Added processor core resource assignment for multi-core optimizations
-Fixed process priority optimizations so that new process like audiophile player won't start with lowest priority
-Redesigned UI with selectable features list controlled by optimization level
 

yeaaa....no, assigning everything to one core is not a good idea (e.g. my browser usually chews up the entire core 0, and assigning the audio player and explorer and everything else to it is definitely not smart). After running fidelizer every running and starting process is assigned to core 0. I didn't get a 2 core HT CPU to do that lol.
I presume audio is assigned to the other core? (that kinda leaves 2 more HT cores unassigned...And my system only has 2 real, 4 ht ones, what happens if people have 4real, 8ht )

 

[JavierS]

I think V 2.0 makes some permanent changes because after rebooting I still get the clicks whenever there is activity other than listening to music. Now even with 1.6 there is no way to get rid of them. Can this be undone?
 

 

[svyr]

I think V 2.0 makes some permanent changes because after rebooting I still get the clicks whenever there is activity other than listening to music. Now even with 1.6 there is no way to get rid of them. Can this be undone?
 

looking at the script 2.0 doesn't make permanent changes. The difference between 1.6 and 2 is 2 gets process.exe
Command Line Process Viewer/Killer/Suspender for Windows NT/2000/XP V2.03

The app then dumps the current process list from tasklist and runs process.exe to set affinity to 1 for all of them. (explorer gets affinity 1 and the audio service and some other ones 2, while some other things get 3 (well, flag values indicating actual cores I presume))
Then any processes launched should I think inherit affinity. Hence after reboot it should go back.

I don't think affinity is permanently stored anywhere. If it is, then we certainly have a problem


Then again, worst case scenario do what he does - dump the list of PIDs to file, then run process.exe from the temp folder (copy it while fidelizer is running) and run it to set affinity to all cpus for all processes...
(tasklist /fo list >> pid.txt
regex delete lines ^[^PD].*$
regex delete extra line breaks
(only leaves lines with PIDs)
regex replace ^(.*)$ with setaf -a \1 1111 (incidentally, 1111 is for 4 cores 1-4... If you have 2 virtual cores - 11, if 8 - 11111111...You get the picture)
(\1 is a backref, setaf is the renamed process.exe fished out of %TMP% when fiddelizer is 'optimizing')
Save it as a batch file and run it. (will reset affinity without a reboot)

 

[JavierS]

Thx Svyr, will try tonight.
I've just formated + fresh installed W7 and I'll make sure I have a restore point before running V 2.0 just in case... maybe it was my PC's fault, it was doing some funny things lately hence the reinstall.
 
Cheers.
 
 

 

[NTLX]

Mmm I had the same clicking problem as well so you're not alone in that department. It went away when I ran the batch file that syvr suggested though. Thx a lot for the fix over there syvr! Signed up just to say this, since the fidelizer thread's slightly dead so I thought more comments would be helpful for those who encounter the same problem. Pity 2.0 didn't really work out for me. Guess I'll jump back to 1.6

.

 

[Willakan]

Affinity is not stored at all. However, I do question the wisdom of disabling large chunks of your computer's services to yield a supposed increase in sound quality - what exactly is the correlation?

 

[svyr]

Affinity is not stored at all. However, I do question the wisdom of disabling large chunks of your computer's services to yield a supposed increase in sound quality - what exactly is the correlation?

i think the idea was to put a dedicated core for audio related services, but it somewhat backfired into assigning almost everything into 1 core lol

 

[Roller]

Quote:

i think the idea was to put a dedicated core for audio related services, but it somewhat backfired into assigning almost everything into 1 core lol

Not to mention reducing I/O activity and less overall system activity. Though, a real dedicated audio machine won't be used with nearly the amount of ongoing processes and such, which seems to be the idea of the author, and that's why there are dedicated music servers. Still, I have a machine tweaked enough, connected to both intranet and internet, and have zero issues with audio, but maybe that's also related to me not using stock OS drivers but manufacturer drivers.

 

[JavierS]

Quote:

looking at the script 2.0 doesn't make permanent changes. The difference between 1.6 and 2 is 2 gets process.exe
Command Line Process Viewer/Killer/Suspender for Windows NT/2000/XP V2.03

The app then dumps the current process list from tasklist and runs process.exe to set affinity to 1 for all of them. (explorer gets affinity 1 and the audio service and some other ones 2, while some other things get 3 (well, flag values indicating actual cores I presume))
Then any processes launched should I think inherit affinity. Hence after reboot it should go back.

I don't think affinity is permanently stored anywhere. If it is, then we certainly have a problem


Then again, worst case scenario do what he does - dump the list of PIDs to file, then run process.exe from the temp folder (copy it while fidelizer is running) and run it to set affinity to all cpus for all processes...
(tasklist /fo list >> pid.txt
regex delete lines ^[^PD].*$
regex delete extra line breaks
(only leaves lines with PIDs)
regex replace ^(.*)$ with setaf -a \1 1111 (incidentally, 1111 is for 4 cores 1-4... If you have 2 virtual cores - 11, if 8 - 11111111...You get the picture)
(\1 is a backref, setaf is the renamed process.exe fished out of %TMP% when fiddelizer is 'optimizing')
Save it as a batch file and run it. (will reset affinity without a reboot)

 
Svyr,
 
In my case Fidelizer optimizes so quick I don't have time to pick anything from the temp folder, there is a .tmp file that shows up for a fraction of a sec and disappears. I've found the process.exe googling for it and I suppose it'll be the same as it is for NT/XP/2003 (should it work fine even if I'm using W7 x86?).
Also I don't quite understand how to run the regex lines, is regex and external app I need to download?
 
Cheers

 

[svyr]

pv and process exe appear for while when it actually optimizes.

for regex, you can use notepad++. its nice and open source

 

[svyr]

if you want process.exe, search for the app name from the post above, if you look for process.exe per se who knows what you'll end up dl

all you really want is a process manager - gui or cmd line, that can mass set affinities