TBM is difficult to determine without test results.[Display]TEXTURE_BANDWIDTH_MULT=180 (Smoother texture handling with medium+ autogen.)I tested that and you're probably in the region of 200 if you've left the cfg TextureMaxLoad defaults.Give more time to background tasks and maybe reduce blurry textures if that's a problem:[Main]FIBER_FRAME_TIME_FRACTION=0.40 - 0.50FFTF is not included in the cfg

If I remember well in FSX I had TBM set to 400 ( 2x Titan GTX )

 

Regarding TML : as I use photoscenery I will try with 12 and perhaps 9,

Then I need TBM at default. Correct ?

 

FFTF I will try at 0.20 as I do not suffer from blurries.

Seems good!

Found this post from Rob from january 2015 :

 

It is about TML and TBM

 

Quote : "

Assuming Max is not overloaded then TextureMaxLoad will get the higher of the two values. * / are equal order of precedence and hence get evaluated left to right (see here: http://msdn.microsoft.com/ru-ru/subscriptions/2bxt6kc4%28v=vs.100%29.aspx)

 

Example

 

TextureMaxLoad=6 (Default value)

TextureBandwidthMult = 160

LimitedFramerate = 30

 

So

TextureMaxLoad = Max(6, (6*160)/30)

 

so

TextureMaxLoad = Max(6, 960/30)

 

so

TextureMaxLoad = Max(6, 32)

 

so

TextureMaxLoad = 32

"

 

If I have a TML of 12 , can I adjust the TBM accordingly ?

Steve with regards to traffic I use ut2 can in set cores 0,1,3,7 as with asn?

 

Thanks

Hello Steve -

 

I have been following all the avsim threads on this topic and finally decided to jump in with both feet. I just need your "blessing" that I have my system set up correctly. 

 

I have a liquid cooled I7-2700K 4 core processor that I had HT off since I installed it and overclocked to 5Ghz.

 

With your advise, If I understand correctly:

 

I have since enable the HT in the bios and have a good, stable overclock of 4,8GHZ now.

 

I have assigned P3D 3.1 at AM=116 (cpu2,4,5,6) in the p3d.cfg 

 

I have installed process lasso and set the AM for Opus and UT2 to CPU 0,1,3,7

 

I am running SLI 980GTX running a TH2GO and 3 monitors 60hz monitors.. I have the frame limiter in NI set to 30, I have unlimited set in the sim, no triple buffer, no vsync.

 

Is this all correct?

 

If I decided to install any other add-ons, will I also assign them in PL to CPU 0,1,3,7.

 

Thanks for your dedication and great information !!!

-Daniel

Hi Daniel and Mike

 

if you are using headache free 116 you can simply fire up everything else knowing they'll not really impact on the sim too much. That does mean they are running on a reserve in the system, core zero, but although some of that direct reserve is lost to the sim it's not much. We can improve slightly with setting the starting affinity of those addons a little:

 

P3D + Weather addon (Opus ASN) + Other addon (traffic, TIR)

 

with 116=01,11,01,00, put Weather on 0,6,7 and Other on 1,6,7

 

0,6,7=11,00,00,01=193=C1

1,6,7=11,00,00,10=194=C2

 

We can hand a little more bandwidth to those addons put them all on 0,1,6,7, but probably not necessary.

 

0,1,6,7=195=C3

 

What we don't do is put them on 2 or 3.

 

Be aware there has been feedback suggests that some programs don't like being lasso'd. That's certainly the case with P3D and FSX, these control their own starting affinity correctly. Any strange behaviour, look instead to make a batch file to start the app and make a shortcut to that batch file (.bat), this makes it as hassle free as starting the app from it's own icon.

 

Those experimenting with sim AM=85, allocates all four cores to the sim, can use:

 

3,5,7=168=A8 - addons

or

3,4,5,6,7=248=F8 - addons (more bandwidth to addons)

 

 

Whether to use 85 rather than 116 depends on just how "aggressive" an addon is. If you've got an addon that truly maxes out its main allocated core, then this cannot help but impact one of the sim main jobs. But with HT enabled it's not as bad as with HT disabled.

 

 

Readers note we are talking about the four core with HT enabled. 6 or 8 core whizz-kids will separate those apps more across the CPU.

 

 

Just to be sure, P3D and FSX don't like being lasso'd, or even just "touched" by the Task Manager 'Set Affinity menu item, or any app like that. Some have seen this appears to increase activity on the cores. This activity is merely new or confused sim jobs ganging up on the same core. There may look like a load more activity, but the sim actually performs worse. Don't do it. Programs that start apps like FSX and P3D must be specially written to avoid complications and handle the way those apps work specifically.

I've just been asked about the four core no HT. So we've got a slightly less well performing four cores that lose out to HT when switching tasks. But that's OK we can still use the same theory. In the HT enabled 116 example we are actually using three cores, but we use the double LP count to split the sim into four LPs. With no HT we can use three cores with AM=14, but this can only split the sim into three parts. With three parts, the first part has more to do than in the HT 116 example with four parts. So even in this respect we cannot get the sim to perform so well, irrespective of HT enabled or not.

 

Three cores to sim:

AM=14=1,1,1,0=1,2,3

we can put addons on 0,2,3=13=D

 

Four cores to sim, as in HT 85:

AM=0=1,1,1,1=no AM specified in cfg

we can put addons on 1,2,3=14=E

 

Again, same basic application of theory; the whole point of assigning AMs to addons is to help them avoid running on the core hosting the main sim thread.

Thanks Steve

Question why core 6 instead of 3?

I am using am 116

LP6 rather than LP3?

 

With 116 the main sim job is running on LP 2. LP2 is core 1, shared with LP3. The whole point of assigning an AM to an addon is so we can avoid the core hosting the sim main threads. Instead we can put stuff on the other cores. With 116, the main addon threads hit core 0, LPs 0 & 1. But these addons need breathing space, so we can also assign cores hosting the background threads of the sim, they gotta go somewhere with only four cores. So we can allocate LPs 6 and 7, the jobscheduler will mostly hit 7 anyway. We can allocate 6, even though this runs on the same LP as the sim background threads, it's only going to be hit when there's bandwidth available. We can assign cores hosting the sim background threads because they take seconds anyway. If we find the addon uses up too much of that sim background thread bandwith, we can assign 0,1,7 to it, or just assign 0 and 1 to it if it's really aggressive.

 

With 116 on the four core HT enabled, we don't really need to be running affinity settings on addons. Since as I mentioned before, their main threads will hit LPs 0 and 1. They will spawn other threads and they will spill over into "holes" the jobscheduler finds, that'll be LP7 followed by LP6, or LPs 4 and 5, and so on.

 

We don't want to corral addon threads deliberately onto the core hosting the main thread with an affinity mask. That's going to fool the jobsheduler into targeting that core, when it would otherwise avoid it.

 

Most addons, weather, traffic, TIR, will put 90% of their effort into their first few jobs, maybe just the first one or two. Thankfully the sim works pretty well on three cores. Shuffling the sim up onto the last three cores leaves core zero free for that major activity. Spill over activity from there onto other cores is negligible, allocating that LP3 is not going to ruin the day.

Thank you for the informative answer

Now I have set active sky next on 0,6,7 where as before I had it on 0,1,3,7

 

And ezdok, ut2 on 0,1,6,7

 

This would be the best allocation?

 

Thanks

Yes, looks good.

 

Remember that observing fps can fool us. We can see a slightly higher fps on the shift-z display just because the background tasks take longer. The fps is not directly related to the efficiency of the background tasks, since it's got to produce 30fps all the time, no matter how much terrain has been read in. There's dozens of concurrent tasks going on when the sim is started running, a more efficient background can complete them more quickly but interrupt the sim main job more often in the first minutes, reducing the fps during that period.

 

Those data gathering threads of the sim are split into sub threads, called fibres. Fibres switch tasks all the time under their parent thread, and so they are not helped by Hyper Threading in the least. But we are not saying HT doesn't help the sim. There's enough going on with rendering, disk i/o and networking, HT On shows a boost of 3-5% on fps and background throughput.

 

Three cores gets kicked into touch by four cores when the sim is really heavily loaded, but so far, I've had no reports that five or more true cores have produced a better result than four.

 

I've analysed five cores over four, and all that happens is we get less holes for the jobscheduler to target with other tasks, and the fifth sim job brings down the background throughput by 2-3%.

I see. Thank you very much for your time and efforts helping the Fs community.

Much appreciated sir.

 

Mike.

 

 

P3D + Weather addon (Opus ASN) + Other addon (traffic, TIR)

with 116=01,11,01,00, put Weather on 0,6,7 and Other on 1,6,7

0,6,7=11,00,00,01=193=C1
1,6,7=11,00,00,10=194=C2

 

Thanks Steve  I'll make the changes to PL for Opus to 0,6,7 and UT2 to 1,6,7 and keep my AM to 116.

hi all

 

 

about the new version of p3d, is it necessary to use all the tweaks above?

 

thanks

I don't believe the update made any changes in these areas so the answer would be yes. I'd try with and without and see how YOUR system fares.

 

Vic