- Welcome to Bitsum Community Forum.
Development (period)
Recent posts
#1
Process Lasso / Re: My E-cores makes me crazy
Last post by Manuel - Today at 05:49:27 AMQuote from: Jeremy Collake on Yesterday at 03:00:07 PMWhat analysis software is this?
Thank you for your quick response!
My analysis software is "SCIA Engineer" and the process that does the calculations is "DesignForms_CalcExe.exe".
QuoteFirst, let's ensure you've checked menu item 'Options / Forced Mode (continuously reapply settings)', in case that software is managing its own affinity.
I tried after your indication, but it didn't seem to change things....
QuoteWith the E-cores removed by affinity, the total CPU % is going to be limited since only the P-cores can be used. In contrast, when you disabled the E-cores in the BIOS, the CPU consumption could reach 100% since the E-cores were not included in the total available capacity.
This aspect is clear, thank you!
QuoteYou should also check for any thread count setting in the analysis software and set it to the total number of P-cores threads you have available (2x the P-cores). Otherwise, it may launch too many threads for the constrained CPU affinity to cope with.
How is the analysis time after the rules you set with Process Lasso?
I was able to get only the P-Cores to work in various ways, see image below, but although the bar graph says that the P-Cores are working at maximum, HWiNFO64 indicates that the work rate is at about 45% (I think this value is correct, because the case fans do not start running at maximum as if I run Cinebench).
The strange thing, besides the fact that the P-Cores are not working at maximum, is that the processing time is always very long (the behavior is very different if I disable the E-Cores in the BIOS), it seems that Windows still wants to try to work with the E-Cores and this slows everything down (I don't know if this is really the case, but it is my impression).
Just for information, I tried to run the software on a Ryzen 7950x that does not have E-Cores, but again the processing time is incredibly too long compared to using (8+8) P-Cores from the 13900K (selected via BIOS)... and with a Ryzen I could not use the "trick" of disabling E-Cores from BIOS.
Do you have any other suggestions for me?
If not, I guess I'll have to give up....
Thanks in advance
Manuel
#2
Process Lasso / Re: My E-cores makes me crazy
Last post by Jeremy Collake - Yesterday at 03:00:07 PMWhat analysis software is this?
First, let's ensure you've checked menu item 'Options / Forced Mode (continuously reapply settings)', in case that software is managing its own affinity.
With the E-cores removed by affinity, the total CPU % is going to be limited since only the P-cores can be used. In contrast, when you disabled the E-cores in the BIOS, the CPU consumption could reach 100% since the E-cores were not included in the total available capacity.
You should also check for any thread count setting in the analysis software and set it to the total number of P-cores threads you have available (2x the P-cores). Otherwise, it may launch too many threads for the constrained CPU affinity to cope with.
How is the analysis time after the rules you set with Process Lasso?
First, let's ensure you've checked menu item 'Options / Forced Mode (continuously reapply settings)', in case that software is managing its own affinity.
With the E-cores removed by affinity, the total CPU % is going to be limited since only the P-cores can be used. In contrast, when you disabled the E-cores in the BIOS, the CPU consumption could reach 100% since the E-cores were not included in the total available capacity.
You should also check for any thread count setting in the analysis software and set it to the total number of P-cores threads you have available (2x the P-cores). Otherwise, it may launch too many threads for the constrained CPU affinity to cope with.
How is the analysis time after the rules you set with Process Lasso?
#3
Process Lasso / My E-cores makes me crazy
Last post by Manuel - Yesterday at 12:12:12 PMDear all,
I use a workstation with i9-13900K processor and the 16 E-core gives me a lot of problems. The problem is well known, Windows 11 has problems handling some applications in the background or hidden and as a result some software loses a lot of performance.
I use the workstation for work with analysis software and, to give an example, if I launch a calculation with all 32 threads available on a model I use as a reference, the calculation takes about 9 minutes. If I disable the E-cores via BIOS, all the P-cores work at 100% and the time decreases to about 1 minute 30"! I don't know what Windows does, but it's a mess!!!
The current solution is to disable the E-core via BIOS, but it is something that irritates me, because 16 cores are off and in other tests, such as Cinebench R23, they all work smoothly and with very good performance (I calculated that the 16 E-core contribute about 40% of the performance).
I have a Process Lasso license with which I hoped to solve the problem, but I have tried everything and the results are always the same. The process performing the calculations starts for a few seconds using 100% of the 13900K's 32 threads and then "sits" at about 35% making everything work a little bit, but badly... (below is a screenshot of an example analysis).
I tried in various combinations what you see below, but nothing ever changed:
- Exclude from probalance
- affinity - only P-core
- efficiency mode off
- I/O priority high
- windows dynamic thread priority boost off
- induce performance mode on
Do you have any suggestions?
I am going crazy!
Thanks in advance
Manuel
I use a workstation with i9-13900K processor and the 16 E-core gives me a lot of problems. The problem is well known, Windows 11 has problems handling some applications in the background or hidden and as a result some software loses a lot of performance.
I use the workstation for work with analysis software and, to give an example, if I launch a calculation with all 32 threads available on a model I use as a reference, the calculation takes about 9 minutes. If I disable the E-cores via BIOS, all the P-cores work at 100% and the time decreases to about 1 minute 30"! I don't know what Windows does, but it's a mess!!!
The current solution is to disable the E-core via BIOS, but it is something that irritates me, because 16 cores are off and in other tests, such as Cinebench R23, they all work smoothly and with very good performance (I calculated that the 16 E-core contribute about 40% of the performance).
I have a Process Lasso license with which I hoped to solve the problem, but I have tried everything and the results are always the same. The process performing the calculations starts for a few seconds using 100% of the 13900K's 32 threads and then "sits" at about 35% making everything work a little bit, but badly... (below is a screenshot of an example analysis).
I tried in various combinations what you see below, but nothing ever changed:
- Exclude from probalance
- affinity - only P-core
- efficiency mode off
- I/O priority high
- windows dynamic thread priority boost off
- induce performance mode on
Do you have any suggestions?
I am going crazy!
Thanks in advance
Manuel
#4
General / Re: Difference between termina...
Last post by Jeremy Collake - Yesterday at 06:49:18 AMClosing first sends a message signaling the process to end, allowing it a chance to gracefully close. Termination forcibly ends the process.
#5
General / Difference between terminating...
Last post by riley - May 16, 2024, 07:10:15 PMDifference between terminating and closing process?
#6
Process Lasso / Re: core engine is not running...
Last post by DaymanSalvort - May 15, 2024, 06:22:20 AMI am in fact grateful to this site which has shared this fantastic information here.
#7
Process Lasso / Re: Process Lasso management c...
Last post by Jeremy Collake - May 15, 2024, 05:47:18 AMHmm, that's unusual.
First, be sure you used the official installer from https://dl.bitsum.com/files/processlassosetup64.exe .
Then check to see if it generated any dump file. It'd be stored in %appdata%\processlasso or %programdata%\processlasso (you can paste those in Explorer's location bar). Alternatively, while the process is still running you can generate one with the Task Manager by opening the Details tab, right-clicking on the process, and selecting 'Create dump file'.
You can then share the dump with us via any cloud drive or upload to https://bitsum.com/minidumps. You can communicate with us by email at support@bitsum.com.
First, be sure you used the official installer from https://dl.bitsum.com/files/processlassosetup64.exe .
Then check to see if it generated any dump file. It'd be stored in %appdata%\processlasso or %programdata%\processlasso (you can paste those in Explorer's location bar). Alternatively, while the process is still running you can generate one with the Task Manager by opening the Details tab, right-clicking on the process, and selecting 'Create dump file'.
You can then share the dump with us via any cloud drive or upload to https://bitsum.com/minidumps. You can communicate with us by email at support@bitsum.com.
#8
Process Lasso / Process Lasso management conso...
Last post by derekperry - May 14, 2024, 11:09:21 PMHello,
Since an update a few weeks back, my Process Lasso management console keep crashing whenever it starts.
I've tried reinstalling, but it doesnt help.
This computer is a system mainly used for surfing, so there's not been any changes to hardware or other software recently either.
Since an update a few weeks back, my Process Lasso management console keep crashing whenever it starts.
I've tried reinstalling, but it doesnt help.
This computer is a system mainly used for surfing, so there's not been any changes to hardware or other software recently either.
#9
Process Lasso / Re: Should ProBalance be enabl...
Last post by Jeremy Collake - May 14, 2024, 08:40:16 AMYes, you should leave ProBalance enabled in Performance Mode. We are not aware of any issues with it, and its conservative default settings all but ensure such. ProBalance serves an important role to help keep background processes at bay during gameplay.
That said, after noticing that most Process Lasso guides for Intel 12th+ processors with E-cores suggested to disable ProBalance, we decided to save people the step of turning it off and just defaulted it to off on those platforms. This is part of a larger plan to make the two on-by-default features, ProBalance and automatic game detection for Performance Mode, off by default so that users are encouraged to become aware of them prior to enablement.
That said, after noticing that most Process Lasso guides for Intel 12th+ processors with E-cores suggested to disable ProBalance, we decided to save people the step of turning it off and just defaulted it to off on those platforms. This is part of a larger plan to make the two on-by-default features, ProBalance and automatic game detection for Performance Mode, off by default so that users are encouraged to become aware of them prior to enablement.
#10
Process Lasso / Re: Anyone Using Process Lasso...
Last post by Coldblackice - May 14, 2024, 02:44:12 AM(EDIT)
I found a recent user's experience re: benefits of Process Lasso improving their game performance on a system struggling with DPC latency issues:
https://www.reddit.com/r/nvidia/comments/152xvm9/game_ready_studio_driver_53667_faqdiscussion/jttez8z/
I found a recent user's experience re: benefits of Process Lasso improving their game performance on a system struggling with DPC latency issues:
https://www.reddit.com/r/nvidia/comments/152xvm9/game_ready_studio_driver_53667_faqdiscussion/jttez8z/