sfio priority что это

Sfio priority что это

Regedit System tweaks

Windows Registry Editor Version 5.00

; Enable Congestion Control Provider(CTCP) on Windows 8.1

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\\0]
«0200»=hex:00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,02,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,?\
00,00,00,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,?\
ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
«1700»=hex:00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,02,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,?\
00,00,00,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,?\
ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

; Disable Hibernation Mode

; SSD Tweaks and fastboot

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]

; Advanced Windows 7/8.1 Power Manager

«Scheduling Category»=»High»
«SFIO Priority»=»High»
«Background Only»=»False»
«Priority»=dword:00000001
«Clock Rate»=dword:00002710
«GPU Priority»=dword:00000001
«Affinity»=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Low Latency]

«Scheduling Category»=»High»
«SFIO Priority»=»High»
«Background Only»=»False»
«Priority»=dword:00000001
«Latency Sensitive»=»True»
«Clock Rate»=dword:00002710
«GPU Priority»=dword:00000002
«Affinity»=dword:00000000

«Scheduling Category»=»High»
«SFIO Priority»=»High»
«Background Only»=»True»
«Priority»=dword:00000001
«Clock Rate»=dword:00002710
«GPU Priority»=dword:00000002
«Affinity»=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Pro Audio]

«Scheduling Category»=»High»
«SFIO Priority»=»High»
«Background Only»=»False»
«Priority»=dword:00000001
«Clock Rate»=dword:00002710
«GPU Priority»=dword:00000005
«Affinity»=dword:00000000

Источник

Сегодня мы покажем Вам парочку настроек Regedit.

-Увеличение частоты кадров в Fortnite.

-Повышение частоты кадров в Counter-Strike: Global Offensive.

-Повышение FPS в Warzone.

-Повышение FPS в Minecraft.

-Уменьшенная задержка ввода.

-Быстрее Windows 10.

-Более простая система.

-Исправить падение FPS.

Начнём:

Для начала зайдём в сам Regedit, для этого прожимаем комбинацию клавиш Win+R и в открывшимся окне пишем «Regedit»

ВНИМАНИЕ ЕСЛИ У ВАС НЕ ОКАЗАЛОСЬ ПАРАМЕТРА ТО СОЗДАЙТЕ ЕГО КАК DWORD.

Все команды которые будут ниже припописываем в эту строку.

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control

В этой ветки нам нужно поменять параметр «SvcHostSplitThresholdInKB»

Изменяете значение в зависимости от вашей оперативной памяти.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

В этом случае нам нужно выставить значениям этим параметрам:

Если не оказалось какого-либо параметра создаёте его как DWORD

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\ApplicationManagement\AllowGameDVR

Здесь мы выставляем значение 0 у «value»

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power

Если нету папки то создавайте с именем «PowerThrottling»

Если нету параметра PowerThrottlingOff, то создайте его как DWORD и поставьте значение 1

HKEY_CURRENT_USER\System\GameConfigStore

Далее в папке GameConfigStore удалите Children и Parents

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games

Здесь нам нужно выставить следующие значений параметров:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile

HKEY_CURRENT_USER\Control Panel\Desktop

HKEY_CURRENT_USER\Control Panel\Accessibility\StickyKeys

HKEY_CURRENT_USER\Control Panel\Accessibility\MouseKeys

HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Response

HKEY_CURRENT_USER\Control Panel\Accessibility\ToggleKeys

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\Maintenance

Я оставлю некоторую информацию о настройках реестра в том же порядке, что

Источник

Multimedia Class Scheduler Service

The Multimedia Class Scheduler service (MMCSS) enables multimedia applications to ensure that their time-sensitive processing receives prioritized access to CPU resources. This service enables multimedia applications to utilize as much of the CPU as possible without denying CPU resources to lower-priority applications.

MMCSS uses information stored in the registry to identify supported tasks and determine the relative priority of threads performing these tasks. Each thread that is performing work related to a particular task calls the AvSetMmMaxThreadCharacteristics or AvSetMmThreadCharacteristics function to inform MMCSS that it is working on that task.

For an example of a program that uses MMCSS, see Exclusive-Mode Streams.

Windows ServerВ 2003 and WindowsВ XP: MMCSS is not available.

Registry Settings

The MMCSS settings are stored in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile

This key contains a REG_DWORD value named SystemResponsiveness that determines the percentage of CPU resources that should be guaranteed to low-priority tasks. For example, if this value is 20, then 20% of CPU resources are reserved for low-priority tasks. Note that values that are not evenly divisible by 10 are rounded up to the nearest multiple of 10. A value of 0 is also treated as 10.

The key also contains a subkey named Tasks that contains the list of tasks. By default, Windows supports the following tasks:

OEMs can add additional tasks as required.

Each task key contains the following set of values that represent characteristics to be applied to threads that are associated with the task.

To conserve power, applications should not set the resolution of the system-wide timer to a small value unless absolutely necessary. For more information, see Performance in the Windows 7 Developers Guide.

Thread Priorities

The MMCSS boosts the priority of threads that are working on high-priority multimedia tasks.

MMCSS determines the priority of a thread using the following factors:

MMCSS sets the priority of client threads depending on their scheduling category.

Источник

Gaming Performance / System Optimization / Useful Tweaks

Game / Performance / Networking tweaks, tips, hacks, apps

REGISTRY TWEAKS

33 comments:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games]
«Affinity»=dword:00000000
«Background Only»=»False»
«Clock Rate»=dword:00003710
«GPU Priority»=dword:00000006
«Priority»=dword:00000002
«Scheduling Category»=»High»
«SFIO Priority»=»High»

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
LargeSystemCache=0

essa regedit é boaa?

Critical most likely will cause you stuttters in game. Its meant for small, not demanding processes and mostly System onees.

Hey! The irq you choose are msi related but didnt you say you shouldnt use them?

MSI related What you mean??

Irq with minus are in the msi mode ( «Its not good if you set an MSI based driver with IRQL priority so keep that in mind.» )

Yes, thats true. At least for the modern hardware. Old GPUs dont use MSI for ex. Since its old method and u can use Affinity tool. I thought i made that clear. I’ll check it out. Thanks. If you use the MSI Utility it should be overrided anyway, or the driver itself will.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile] «NoLazyMode»=dword:1

Where is this coming from? I’ve trawled the web for 2 days now, I see no documentation on it whatsoever.

As far as I’m considered, this is a ambiguous random entry that anyone can write in their registry in whatever key they like.

What funcionality did it serve, where did it come from? Was it something of actual usage in older versions of the OS in the Windows ecosystem?

ambiguous. that sounds. ambiguous 😀
Ok,I’ll skip the part that i say you are probably a noob (the fact that you ask about LazyMode but not about Latency Sensitive along with that Google reference kinda suggests that) and that Google is not = knowledge and go straight to the answer. There is another setting called AlwaysOn. This comes from Win7 & 8 days, when there is no multimedia activity the drivers stops working (idle itself). These settings prevents it from doing so & the priorities are always active. Some of my tweaks have settings that doesnt work in Win10 but i keep them for compatibility reasons because there are many people who still use Win7. With that said I have no reason to believe that they doesnt work. These tweaks in SystemProfile are not required for gaming these days because are very hard to spot, the impact is negligible & I recommend them only for competitive gaming anyway. You also can disable the driver but Im not sure thats a good thing.

Источник

Gaming Tweaks

Online Gaming can often benefit from some fine-tuning of Windows TCP/IP settings and the Network Adapter properties. This article is intended to supplement our general broadband tweaks and list only TCP/IP settings that are specific to online gaming and reducing network latency. Some of these settings are also mentioned in our general tweaking articles, however, the emphasis here is on latency rather than throughput, and we have complemented the tweaks with more gaming-specific recommendations and settings that give priority to multimedia/gaming traffic, and may be outside of the scope of other broadband tweaks that focus on pure throughput.

Disable Nagle’s Algorithm

(TCP Optimizer «Advanced Settings» tab)
This tweak works with all versions of Windows from Windows XP to Windows 8.1/10/2012 server. This is the same as listed in our general tweaking articles per OS.

Nagle’s algorithm is designed to allow several small packets to be combined together into a single, larger packet for more efficient transmissions. While this improves throughput efficiency and reduces TCP/IP header overhead, it also briefly delays transmission of small packets. Disabling «nagling» can help reduce latency/ping in some games. Keep in mind that disabling Nagle’s algorithm may also have some negative effect on file transfers. Nagle’s algorithm is enabled in Windows by default. To implement this tweak and disable Nagle’s algorithm, modify the following registry keys.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\
There will be multiple NIC interfaces listed there, for example: <1660430C-B14A-4AC2-8F83-B653E83E8297>. Find the correct one with your IP address listed. Under this key, create a new DWORD value:
«TcpAckFrequency»=1 (DWORD value, not present by default interpreted as 2, 1=disable nagling, specifies number of outstanding ACKs before ignoring delayed ACK timer). For gaming performance, recommended is 1 (disable). For pure throughput and data streaming, you can experiment with small values over 2. Wifi performance may see a slight improvement with disabled TcpAckFrequency as well.

In the same location, add a new DWORD value:
TCPNoDelay=1 (DWORD, not present by default, 0 to enable Nagle’s algorithm, 1 to disable)

To configure the ACK interval timeout (only has effect if nagling is enabled), find the following key:
TcpDelAckTicks=0 (DWORD value, not present by default interpreted as 2, 0=disable nagling, 1-6=100-600 ms). Note you can also set this to 1 to reduce the nagle effect from the default of 200ms without disabling it.

For Server Operating Systems that have Microsoft Message Queuing (MSMQ) installed, or if you have the MSMQ registry hive present, also add TCPNoDelay to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
TCPNoDelay=1 (DWORD, not present by default, 0 to enable Nagle’s algorithm, 1 to disable)

Note: Reportedly, disabling Nagle’s algorithm can reduce the latency in many MMOs like Diablo III and WoW (World of Warcraft) by almost half! Yes, it works with Windows 7 and Windows 8.

Network Throttling Index Gaming Tweak

(TCP Optimizer «Advanced Settings» tab)
Works with all current versions of Windows from Vista to 8.1/10/2012 Server.

Windows implements a network throttling mechanism to restrict the processing of non-multimedia network traffic to 10 packets per millisecond (a bit over 100 Mbits/second). The idea behind such throttling is that processing of network packets can be a resource-intensive task, and it may need to be throttled to give prioritized CPU access to multimedia programs. In some cases, such as Gigabit networks and some online games, for example, it is beneficial to turn off such throttling all together for achieving maximum throughput.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
«NetworkThrottlingIndex»=dword:ffffffff (DWORD, default: 10, recommended: 10 for media sharing, ffffffff for gaming and max throughput, valid range: 1 through 70 decimal or ffffffff to completely disable throttling)

It is only recommended to change this setting in saturated Gigabit LAN environments, where you do not want to give priority to multimedia playback. Reportedly, disabling throttling by using ffffffff can also help reduce ping spikes in some online games. Games that may be affected by this throttling: Source Engine games (TF2, Left 4 Dead, CS:S), HoN, CoD, Overlord series.

System Responsiveness Gaming Tweak

(TCP Optimizer «Advanced Settings» tab)
Exists in all versions of Windows from Vista to 8.1/10/2012 Server.

Multimedia applications use the «Multimedia Class Scheduler» service (MMCSS) to ensure prioritized access to CPU resources, without denying CPU resources to lower-priority background applications. This reserves 20% of CPU by default for background processes, your multimedia streaming and some games can only utilize up to 80% of the CPU. This setting, in combination with the «NetworkThrottlingIndex» can help some games and video streaming. We recommend reducing the reserved CPU for background processes from the default of 20%.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
«SystemResponsiveness»=dword:00000000 (default: 20, recommended: decimal 10 for general applications, 0 for pure gaming/streaming)

Note: In Server operating systems (Windows 2008/2012 Server), SystemResponsiveness is set to 100 by default, denoting that background services should take priority over any multimedia applications.

Turn off LargeSystemCache

(TCP Optimizer «Advanced Settings» tab)
For local network large file transfers, this registry settings allows for better throughput and eliminates some file sharing event log errors (Event ID 2017 error). However, reportedly it has issues with some ATI Video card drivers and certain applications performance. Therefore we recommend turning it off (set to zero) for gaming.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
LargeSystemCache=0 (DWORD, default value: 0, recommended value: 1 for LAN throughput, 0 for gaming)
A value of zero establishes a cache of

8 MB, a value of 1 allows the cache to expand up to the amount of physical memory minus 4 MB, as necessary.

Disable Game Bar and Game Mode under Windows 10 Creators update

Windows 10 Creators’ update introduced a «Game Bar» to to help Xbox integration and gaming in general, however, they can reportedly cause stuttering during gaming, especially with Windows 10 builds prior to v1709.

More Gaming Tweaks

This section includes gaming-specific tweaks not listed in our general tweaking articles (and not implemented by the TCP Optimizer).

In the same Registry hive as the above two tweaks, you can also change the priority of Games, compared to other types of traffic. These tweaks only affect games that communicate with e Multimedia Class Scheduler Service (MMCSS). Below is a list of the settings and default/recommended values:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games]
«Affinity»=dword:00000000 (DWORD, default: 0, recommended: 0. Both 0x00 and 0xFFFFFFFF indicate that processor affinity is not used)
«Background Only»=»False» (REG_SZ, default: «False», recommended: «False», possible values are True or False). Indicates whether this is a background task.
«Clock Rate»=dword:00002710 (DWORD, default: 2710, recommended: 2710). The maximum guaranteed clock rate the system uses if a thread joins disk task, in 100-nanosecond intervals.
«GPU Priority»=dword:00000008 (DWORD, default: 2, recommended: 8. range: 0-31). The GPU priority. Not used in Windows XP and 2003.
«Priority»=dword:00000002 (DWORD, default: 2, recommended: leave alone if using «Scheduling Category» below, set to 6 otherwise for gaming, possible values are 1-8). The task priority, ranging from 1(low) to 8(high). Note for tasks with Scheduling Category of «High», this value is always treated as 2.
«Scheduling Category»=»High» (REG_SZ, default: «Medium», recommended: «High». possible values: Low, Medium, High)
«SFIO Priority»=»High» (REG_SZ, default: «Normal», recommended: «High») The scheduled I/O priority, possible values are Idle, Low, Normal, or High.

Congestion Control Provider

The TCP Congestion Control Algorithm controls how well, and how fast your connection recovers from network congestion, packet loss, and increase in latency. Microsoft changed the default «congestion provider» from CTCP to CUBIC with the Windows Creators update.

Possible settings are: none, CTCP, CUBIC, DCTCP, New-Reno
Recommended: CTCP for gaming and latency sensitive apps, CUBIC for pure throughput

To see the current setting, in PowerShell use: Get-NetTCPSetting | Select SettingName, CongestionProvider (in later Windows 10 builds, the default used template «SettingName» is «Internet». For more info se our Windows 10 Tweaks article)

Note: If using CTCP and with lossy connections (good possibility of congestion/packet loss), you may also want to enable ECN.

ECN Capability

(Editable with the TCP Optimizer)
ECN (Explicit Congestion Notification, RFC 3168) is a mechanism that provides routers with an alternate method of communicating network congestion. It is aimed to decrease retransmissions. In essence, ECN assumes that the cause of any packet loss is router congestion. It allows routers experiencing congestion to mark packets and allow clients to automatically lower their transfer rate to prevent further packet loss. Traditionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a bit in the IP header (in the DiffServ field) instead of dropping a packet in order to signal congestion. The receiver echoes the congestion indication to the sender, which must react as though a packet drop were detected. ECN is disabled by default in modern Windows TCP/IP implementations, as it is possible that it may cause problems with some outdated routers that drop packets with the ECN bit set, rather than ignoring the bit.

Possible settings are: enabled, disabled, default (restores the state to the system default).
Default state: disabled
Recommendation: «enabled» for gaming only with routers that support it, after testing. It’s effects are more noticeable in the presence of congestion/packet loss. Disable for pure throughput with no packet loss.

ECN works well for short-lived, interactive connections like gaming and HTTP requests with routers that support it, in the presence of congestion/packet loss. It can be disabled if tuning for pure bulk throughput with large TCP Window, no regular congestion/packet loss, or with outdated routers that do not support ECN.

To change using netsh:

netsh int tcp set global ecncapability=enabled
(alternative syntax: netsh int tcp set global ecn=enabled)

To change using PowerShell cmdlets in Windows 8.1/2012 Server R2 :

Notes:
ECN is only effective in combination with AQM (Active Queue Management) router policy. It has more noticeable effect on performance with interactive connections, online games, and HTTP requests, in the presence of router congestion/packet loss. Its effect on bulk throughput with large TCP Window are less clear. Currently, we only recommend enabling this setting in the presence of packet loss, with ECN-capable routers. Its effects should be tested. We also recommend using ECN if you are enabling the CoDel scheduling algorithm to combat bufferbloat and reduce latency.
Use caution when enabling ECN, as it may also have negative impact on throughput with some residential US ISPs. Some EA multiplayer games that require a profile logon do not support ECN yet (you will not be able to logon). Note that if supported, ECN can reduce latency in some games with ECN-capable routers in the presence of packet loss (dropped packets).

Disable Receive Segment Coalescing State (RSC)

(Editable with the TCP Optimizer) This is applicable to Windows 8/10/2012 Server, not available for earlier Windows versions.

Receive Segment Coalescing (RSC) allows the NIC to coalesce multiple TCP/IP packets that arrive within a single interrupt into a single larger packet (up to 64KB) so that the network stack has to process fewer headers, resulting in 10% to 30% reduction in I/O overhead depending on the workload, thereby improving throughput. Receive Segment Coalescing (RCS) is able to collect packets that are received during the same interrupt cycle and put them together so that they can be more efficiently delivered to the network stack. While this reduces CPU utilization and improves thorughput, it can also have a negative impact on latency. That is why we recommend you disable it where latency is more important than throughput.

Possible states: enabled, disabled, default. Default state: disabled
Recommended: disabled for pure gaming latency, enabled for better throughput.
To enable using netsh:

netsh int tcp set global rsc=disabled

To change using PowerShell cmdlets:

Notes: Only supported by some network adapters. May need «Checksum Offload» enabled as well to work.

Disable Large Send Offload (LSO)

(Editable with the TCP Optimizer) Windows 8/10/2012 Server, not available in earlier Windows versions

Large Send Offload lets the network adapter hardware to complete data segmentation, rather than the OS. Theoretically, this feature may improve transmission performance, and reduce CPU load. The problem with this setting is buggy implementation on many levels, including Network Adapter Drivers. Intel and Broadcom drivers are known to have this enabled by default, and may have many issues with it. In addition, in general any additional processing by the network adapter can introduce some latency which is exactly what we are trying to avoid when tweaking for gaming performance. We recommend disabling LSO at both the Network Adapter properties, and at the OS level with the setting below.

Default: adapter-dependent
Recommended: disable (both in network adapter properties and in the TCP/IP stack at the OS level)

Notes: Default state is network adapter dependent. Needs Checksum Offload to be enabled to work.

Receive-Side Scaling State (RSS)

(Editable with the TCP Optimizer)
It is sometimes useful to disable RSS if you need to reduce CPU load. This is useful on systems with older/slower CPUs where games tax the processor up to 100% at times. This could be checked with «Task Monitor». Disabling RSS will only have an effect if your network adapter is capable/using RSS, and the CPU is being used up to 100%. Otherwise, you can leave it enabled.

netsh int tcp set global rss=disabled

Advanced Concepts

Disable Coalescing: Some network adapters support advanced settings, such as DMA Coalescing, DCA Coalescing, Receive Segment Coalescing (RSC). In general, any type of packet or memory coalescing can reduce CPU utilization (also power consumption) and increases throughput, as it allows the network adapter to combine multiple packets, however, coalescing can also have negative impact on latency, especially with more aggressive settings. That is why it should be either disabled, or used very conservatively for gaming. Any type of network adapter packet/memory coalescing allows the NIC to collect packets before it interacts with other hardware. This may increase network latency. For gaming, disable «DMA coalescing» and «Receive Side Coalescing State (RSC)», where applicable.

TCP Offloading: TCP Offloads can improve throughput in general, however, they’ve been plagued by driver issues in the past, and, they also put more strain on the network adapter. For pure gaming, disable any TCP Offloads, such as «Large Send Offload (LSO)», for example. For pure gaming and lowest possible latency, the only safe offload that should be left to the network adapter is «Checksum Offload».

Disable Interrupt Moderation: If your Network Adapter supports this setting, it should be disabled for the lowest possible latency (at the expense of a bit higher CPU utilization).

For some of those settings specific to your OS, see our tweaking articles. To disable at the network adapter, see our Network Adapter Optimization article.

Use adequate Send/Receive buffers: low send/receive buffers values conserve a bit of memory, however they can result in dropped packets and decreased performance if exhausted, so they shouldn’t be set to values less than 256 in general. Higher-end NICS/systems can increase the values a bit to 512, or up to 1024.

Router Settings

Most broadband users have some type of NAT router that sits between them and the internet. There are some settings that may help your router better prioritize gaming traffic and improve gaming experience.

Enable upstream QoS in your router. It may be useful to enable upstream QoS at the router, if available, to prioritize the different types of traffic. Upstream QoS is important, because typically residential connections have much lower upstream cap, and when upstream bandwidth is all utilized, it can introduce some delay in the downstream traffic as well. Note this is only recommended for newer routers, where the router has ample computing power to handle the QoS overhead.

Enable WMM if using Wi-Fi. If you must use Wi-Fi, enable WMM, and try to avoid USB Wi-Fi adapters.

Use Open Source Firmware. Many NAT router models support open source firmware, such as dd-wrt, Tomato, etc. If your router’s default firmware does not support advanced functionality that you may need (QoS, WMM, VLANs, etc.), you may be able to flash dd-wrt instead. It is not uncommon for open source firmware to make your connection more stable and reduce router overhead/delay.

Note: If using dd-wrt, or on Wi-Fi, check our wireless network speed tweaks, some of the advanced router settings are applicable to wired connections as well.

General Online Gaming Recommendations

Intel Recommended Network Adapter Settings

Optimized for quick response and low latency (Gaming):

Optimized for throughput:

For low CPU utilization:

Notes

In some situations, latency can even be reduced by using a VPN provider. Many ISPs provide fast/reliable internet locally between you and their servers, however lack in both speed in latency when it comes to their peering arrangements and backbones for longer distance connections. They could also be throttling certain traffic types. In such situations, a local to you quality VPN provider may allow you to avoid the ISP bottleneck by bypassing a lot of internal/cluttered routing and skip to a distant location faster, providing a lower latency connection.

Some of the tweaks in our general broadband tweaks articles can benefit gaming as well, like disabling «Windows Scaling Heuristics», disabling TCP 1323 Timestamps to reduce the TCP headers overhead, etc.

Most of the Registry tweaks above (with the exception of «More Gaming Tweaks») can be applied easily by using the TCP Optimizer

See Also

We appreciate any feedback and always listen to user suggestions.

Источник