Recent Posts

Pages: 1 ... 8 9 [10]
Process Lasso / Re: Process Lasso, Vulcan and multi threading/multi core access
« Last post by edkiefer on January 16, 2019, 10:31:17 AM »
Cool, do report back your findings, I will be interested in the results.
Process Lasso / Re: Process Lasso, Vulcan and multi threading/multi core access
« Last post by Pokeyoats on January 16, 2019, 08:44:01 AM »
Wonderful suggestions,

I am turning off all the affinities now and testing and will report my findings in this thread after I have.

Also, for anyone stuck with Prepar3d or even X-Plane up to 11.26 Process Lasso is completely necessary to have your sim run over 20fps, in fact, I get 40-60 using Process Lasso affinities.

The trick is as simple as putting plug-ins (SkyForce, Active Sky etc.) forced onto one core, and then dedicating at least one (but up to remaining) cores to the flight sim, I can even use this technique with VR games by moving the Oculus server onto it's own core and not letting the game/app access (what I refer to as) the "ancillary processing core".

This seems to also dramatically help with CPU temp as well by about 5C.
Process Lasso / Re: Process Lasso, Vulcan and multi threading/multi core access
« Last post by edkiefer on January 15, 2019, 03:50:27 PM »
I don't have direct experience with Xplain engine but many flight sims are using older engines and you will find D3d rendering is on one core many times.
Now with Vulcan or Dx12, being low-level API they can be coded to use many threads/cores for what was limited before.

What I would do is remove any affinity settings you have, run the sim only (no VR or other 3rd party apps) and monitor usage across the free cores you have. that should give you a good idea of how to set affinity if it needs it now.
Process Lasso / Re: Process Lasso, Vulcan and multi threading/multi core access
« Last post by Jeremy Collake on January 15, 2019, 03:38:08 PM »
I don't have any guidance, though hope you do hear from the someone who does, and/or update this thread with your experiences.

I would be curious to hear just how multi-threaded it now is.

Most likely, aside from any theory, it will take experimentation to know what settings are appropriate for the X-plane 11.30 update. And these could vary by hardware.
Process Lasso / Process Lasso, Vulcan and multi threading/multi core access
« Last post by Pokeyoats on January 15, 2019, 03:25:28 PM »
Good Day,

I was wondering if someone could advise me of this scenario. As a flight simmer, I use Process Lasoo to great affect with these sims that seem to be very intent on using one CPU.

Without waffling on, with a lot of flight simmers, Process lasoo is essentially used to move plug-ins and in the case of VR, the server applications etc. onto cores whilst moving the main flight sim executable to a core that is least used (using affinity).

As of today, Laminar Research just released X-plane 11.30 which now incorporates the Vulcan API which is renown for its multi-threading ability.

My question is, does anyone have experience with the Vulcan API and process lasso. Should I undo all of my prior work with affinities and let Vulcan attempt to do it’s thing or is there any advice that someone could give who perhaps has experience with Vulcan and process lasso affinities and could kindly advise me.

Thank you kindly,
Jere Lawrence
Process Lasso / Re: PL Update Notification Minimizes Game
« Last post by Danaity on January 14, 2019, 12:50:17 PM »
Did it notify you an update is available and you then had to click a button to update, or that one had just been installed (after an automated update)?

The former is a normal dialog window, the latter is a system tray notification. You can also check if you have automated updates enabled in the Update menu.

Let me know and I'll try to track down the logic that caused this.

Hi It was a notification that an update was available and I could press update,
which opens up PL from tray and shows the notification box.
I did also have notifications enabled but was obviously hoping for a more subtle approach to notifying me.
Would obviously love to be notified, as manually,
I would just forget it and end up with a massively outdated version but I have disabled it for now. :)
Feature Requests / Re: Tray Icon improvements
« Last post by Jeremy Collake on January 14, 2019, 09:03:12 AM »
Thanks for the suggestions/reminder/summary. #1 will take all of 5 minutes, so I can immediately commit to it. The others are good ideas, and I will consider them going forward. I am always being pulled in many directions, especially right now with a lot of fundamentally new R&D.
Coreprio / NumaPref - Launches process with a preferred NUMA node
« Last post by Jeremy Collake on January 13, 2019, 04:44:46 PM »
NumaPref launches a child process with a preferred NUMA node extended attribute (PROC_THREAD_ATTRIBUTE_PREFERRED_NODE).

Note that this same functionality is provided in cmd.exe's Start /NODE. It is exposed here as part of additional experimentation so that we have further control.

When combined with Corepios's NUMA Dissociater, this operation is able to achieve better consistency in the massive (2X) improvements in 7-zip and Indigo Benchmarks on the AMD Threadripper 2990wx, 2970wx, and EPYC 7551.

Consistency is still not 100% though, at least for the 2990wx (EPYC has more consistency with the NUMA Dissociater fix) There is, however, consistency per NUMA node. A fast node will stay fast, it seems. Fast nodes are not dependent on the DMA nodes of the 2990wx. Bizarre.

This is still being digested. Experimental and results are tentative. I encourage user results.



 USAGE: numapref.exe NUMA_NODE_NUM target.exe [target_params, ...]
 fixedlaunch.exe 1 7zg.exe b
 fixedlaunch.exe 1 "indigo bnechmark.exe"

7z before:

7z after:

Feature Requests / Tray Icon improvements
« Last post by Autumner on January 13, 2019, 08:12:17 AM »
There are several requests about this in the past, I'll try to add a few of my own and summarise what I can:

1. Option to not show the "ProBalance Action Is Occurring" icon, i.e. always show CPU usage (or responsiveness)
2. Additional option for RAM usage
3. Option to change graph colour
4. Option to show additional, separate tray icons (Responsiveness, CPU, Memory)
5. Option to show number instead of graph (full icon-size numbers work best here, if they are "enclosed" into the icon they are usually hard to read on small/medium-size displays)
Process Lasso / Re: Sorting minor issue
« Last post by Autumner on January 13, 2019, 07:59:54 AM »
I'll renew my sorting request here, and wish you a Happy New Year!
Pages: 1 ... 8 9 [10]