Recent posts

#1

Process Lasso / Re: CPU Limiter and Watchdog

Last post by felipeav - Today at 09:20:53 AM

Here the INI file:

Code Select Expand

[Administration]
Version=6020200
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
DoNotAdjustAffinityIfCustomized=true
OocDisableCoreParkingWhileIn=false
UseEfficiencyMode=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=11
PerProcessUsageBeforeRestraint=8
TimeOverQuotaBeforeRestraint=900
PerProcessUsageForRestore=4
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
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
ChangeTrayIconOnRestraint=true
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowCPUCoreUtilGraphs=true
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=false
ShowPowerProfile=true
GraphShowTooltips=true
ShowCPUUtilityAsPrimary=true
[Advanced]
AutomaticUpdate=true
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
[Sampling]
SamplingEnabled=false
SamplingIntervalSeconds=900
SamplingOutputPath=
SamplingIncludePattern=*
SamplingExcludePattern=
[Performance]
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
IsConfigWritable=true
ForcedMode=true
IgnoreProblematicProcesses=false
IgnoreSuspendedProcesses=false
SetTimerResolutionAtStartup=0
[ForegroundBoosting]
BoostForegroundProcess=false
ForegroundBoostPriorityClass=0x8000
BoostOnlyNormal=true
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
IncludeCommandLines=false
LogSmartTrim=true
LogCPULimiter=true
LogEfficiencyMode=true
LogGroupExtender=true
LogCPUSets=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=false
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
SmartTrimClearFileCache=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimExclusions=
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=pathofexilesteam.exe;90.00;2000;2;5000
[ProcessDefaults]
NamedAffinities=
DefaultPriorities=
DefaultIOPriorities=
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinitiesEx=
CPUSets=
KeepRunningProcesses=
[ProcessAllowances]
EfficiencyMode=
[ProcessDefaults]
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
ProhibitInternetExplorerExceptWhenAny=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
[PowerManagement]
StartWithPowerPlan=
Display=
PC=
[PowerSaver]
PowerSaver_IdleTime=300
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=


#2

Process Lasso / Re: CPU Limiter and Watchdog

Last post by Jeremy Collake - Today at 08:37:45 AM

Can you copy/paste your INI config file here? You can get to it by "File / Manually Edit Configuration". Alternatively, email it to support@bitsum.com or attach screenshots. Then we can evaluate it.

#3

Process Lasso / CPU Limiter and Watchdog

Last post by felipeav - Yesterday at 09:48:48 PM

Hello, I started using Process Lasso recently, and I'm having a problem with CPU Limiter and Watchdog. I don't know if I'm doing something wrong, but neither one is working for me after creating the rule. I configured it just like in the demo video, but I'm still unable to make it work.

#4

Process Lasso / Re: Process Lasso Error on Aff...

Last post by Jason967 - Yesterday at 06:17:49 AM

It seems you are having problems with the Lasso process and resource management on your computer. You've experimented with prioritizing specific apps like New World and Battlefield 2142, but didn't get the results you expected.

#5

Process Lasso / Re: My E-cores makes me crazy

Last post by Manuel - May 31, 2024, 03:15:36 PM

I imagine the SCIA developers would be responsive to this issue. Is there a reason to believe they won't be?

I'm pretty sure the developers are working on the problem, but it's already been 9 months since I reported this behavior to tech support and nothing has changed yet... they say it's going to be a long job.

I decided a couple of months ago that I would make do somehow and that's why I bought the Process Lasso license, I was sure I would be able to improve something.

I'll stay tuned to this discussion in case anything new comes along!

Thanks again Jeremy

Manuel

#6

Process Lasso / Re: My E-cores makes me crazy

Last post by Jeremy Collake - May 31, 2024, 02:52:35 PM

Do you think this is a problem only with SCIA (and therefore I was very unlucky) or have you observed this behavior before in some other software?

It is very rare, but similar problems are not unheard of. Some legacy games, for instance, don't cope well with too many CPU cores.

You write that you will have to think about the solution... do you think it can be found without rewriting the software code of SCIA?

No elegantly. It would require API hooks and/or code patches to alter the behavior of the application.

I imagine the SCIA developers would be responsive to this issue. Is there a reason to believe they won't be?

#7

Process Lasso / Re: My E-cores makes me crazy

Last post by Manuel - May 31, 2024, 02:04:45 PM

(EDIT FROM JEREMY: I accidentally edited this post while replying and lost much of its original content)

Do you think this is a problem only with SCIA (and therefore I was very unlucky) or have you observed this behavior before in some other software?

You write that you will have to think about the solution... do you think it can be found without rewriting the software code of SCIA?

#8

Process Lasso / Re: My E-cores makes me crazy

Last post by Jeremy Collake - May 31, 2024, 12:35:24 PM

After some experimentation, I found that the problem is the core count, rather than E-cores.

This effect is best seen on the 7950X3D. Reducing the number of cores by 1/2 decreases the calculation time by over 90%.

7950 with all 16 cores enabled, SCIA launches 111 threads and I stopped it at 360 seconds.
7950 with 8 cores enabled, SCIA launches 66 threads and it completed in about 35 seconds.
Intel i5-12600k with all cores enabled was able to complete the calculation in 35 seconds.

It seems likely that SCIA is launching an unnecessarily high number of threads, resulting in synchronization overhead, contention and/or an excess of context switching, thereby substantially reducing performance.

This is why no CPU affinity (or other) rules in Process Lasso have much effect. What *does* have an effect is reducing the number of launched threads, but afaik SCIA is using a hard-coded formula to compute the number of threads to launch based on the available core count.

I'll have to chew on this further and consider ways to resolve it. Ideally, they adjust the application or expose a setting to control the thread count, if one isn't available already.

#9

Process Lasso / Re: My E-cores makes me crazy

Last post by Matteo - May 31, 2024, 06:56:09 AM

Hi everyone,

I have the same problem on my device with this calculation software, SCIA Engineer v24.0. I really hope there can be positive news soon to solve it.
I am looking forward to your valuable support.

Thank you in advance.

Matteo

#10

General / Re: Any one up for a Newbie?

Last post by dallasflynn - May 31, 2024, 06:29:16 AM

When you have a specific question or issue you'd like assistance with, try to post it in the most relevant subsection or forum. This ensures your post gets seen by the right people who can provide the best guidance.