Recent Posts

11

General / Re: Any way to choose power plan when performance mode active ?

« Last post by edkiefer on June 18, 2020, 04:13:50 PM »

It seems it is not possible to pick power plan to use, when performance mode is active. I can't find it anywhere...

Hi, If you had performance mode for a specific process and you ran another program with a profile power plan too. Your first performance mode program is still running so that power plan should still be running.

The best, most efficient ways to sue power plans IMO is to think high/low, so use two or a combo with idlesaver. If you use multiple plans with many processes it's not going to work really as intended.

12

General / Any way to choose power plan when performance mode active ?

« Last post by empleat on June 18, 2020, 01:18:30 PM »

It seems it is not possible to pick power plan to use, when performance mode is active. I can't find it anywhere...

13

Process Lasso / Re: iRacing Ignores CPU Affinity Rules even when forced mode selected

« Last post by Jeremy Collake on June 16, 2020, 01:11:12 PM »

There is not, I'm sorry.

Note that for some games and apps that set their own CPU affinities, causing CPU affinity rules to fail to persist, users can turn on 'Options / Forced mode'. However, that is a different matter than anti-cheat protection.

14

Process Lasso / Re: iRacing Ignores CPU Affinity Rules even when forced mode selected

« Last post by martijn imagehunters on June 15, 2020, 04:25:07 PM »

No worries.

I just wanted to have a thread that could be easily found by other iRacing people trying to do the same thing.

It seems that CPU affinity is blocked by iRacing's EAC (Easy Anti Cheat) software - not sure why, but apparently that's the culprit.

Thank you I was searching for this
Is there a work around probably not i guess?

15

Process Lasso / Re: Smart trim doesn't work

« Last post by empleat on June 12, 2020, 02:48:05 PM »

I didn't expect much anyway. I don't know any program, that could trim standby memory intelligently. It is more of Windows issue. And they won't fix it probably. Or they would already probably and for what they all care you can use page file and microsoft is $@@#^t@!!#$!

16

Process Lasso / Re: Smart trim doesn't work

« Last post by edkiefer on June 12, 2020, 06:23:31 AM »

I don't see anything in config that would stop smarttrim. I noticed you have Probalance set off, not that that would affect smarttrim.

At this point, only thing I can recommend is to make a new profile and see if that fixes it.
Menu >Files>Profile>create lasso profile

17

Process Lasso / Re: Smart trim doesn't work

« Last post by empleat on June 11, 2020, 08:38:01 PM »

Ok, on ini file, just open it with notepad and copy/paste it into the post. You can easily open it by going to the menu "file">"manually edit config file".

Also, I would like to see logs, take a pic of that would be helpful and I could tell you if smarttrim is trimming a process or if standby is doing anything.
Just so you know, to only trim standby you don't need "trim this working set" enabled but I would leave it for the test.
I would uncheck "only purge while in performance mode" just to simplify things.

I have not tested smarttrim w/o pagefile but i doubt that would change anything.
Edit: Tested w/o pagefile and works as it should.

FWIW; I game with BF1, BF4 and BFV, when windows 1803 came out there was an issue with standby list that would cause a stutter after free memory was taken by standby list cache. This got fixed or at least improved for many users in 1909.

I sent you log already.

For settings you gave me, Process Lasso makes no logs and free memory is 43, yet it does nothing.

ini file:

Code: [Select]

[Administration]
Version=4830200
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=false
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=18
PerProcessUsageBeforeRestraint=20
TimeOverQuotaBeforeRestraint=900
PerProcessUsageForRestore=5
PlayOnRestraint=C:\Windows\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\Windows\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowCPUCoreUtilGraphs=true
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=1000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
IgnoreSuspendedProcesses=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=false
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=true
ClearStandbyFreeRAMThresholdMB=15000
ClearStandbyOnlyInPerfMode=false
SmartTrimAutoMinimumRAMLoad=10
MinimumProcessWSSInMb=100
SmartTrimIntervalMins=1
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=
DefaultIOPriorities=
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
PowerSaver_IdleTime=0
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=


18

Process Lasso / Re: Core 0 stuck at 100% usage all the time

« Last post by edkiefer on June 11, 2020, 06:44:48 PM »

Ok, might try one of these to see if it helps.
https://www.thewindowsclub.com/fix-acpi-sys-error/

19

Process Lasso / Re: Core 0 stuck at 100% usage all the time

« Last post by DeadHead on June 11, 2020, 06:16:50 PM »

The issue existed prior to installing the 2004 update, unfortunately. I updated hoping the 2004 would solve things, but no.

20

Process Lasso / Re: Core 0 stuck at 100% usage all the time

« Last post by edkiefer on June 11, 2020, 09:01:01 AM »

Hi Deadhead, I don't have any experiences with your problem but did the system have any of these issues/conditions?

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004

I have seen in the past users with similar type issues fix it by installing on top again.
You can check this forum as it has a lot of Windows users there.
https://www.tenforums.com/performance-maintenance/

Maybe revert to older 1909 until things shape up as 2004 seems to have many issues.