Page 10 of 10 FirstFirst ... 678910
Results 181 to 184 of 184

Thread: TCP Optimizer needs new version since v1709 Windows Update [updated]

  1. #181
    Administrator Philip's Avatar
    Join Date
    May 1999
    Location
    Jacksonville, Florida, United States
    Posts
    9,980
    Blog Entries
    6
    Niko, PM me your normal IP and I will check it out, could be an issue with spam IPs being used by your ISP or something like that.

  2. #182
    Ako ima problem 6e te potursq. Nai veroqtno e ot moite nastroiki. Imam nov internet dostav4ik.

  3. #183
    I see the new Intel drivers introduce RSS Load ballancing Profile. Im using v1709 because the latest Windows Updates patch the Intels Spectre & Meltdown issues and thus hurt the general performance.
    Im on "Numa Scaling" now. WHat settings you guys use?

    The Closest_Processor_Static profile has the lowest memory
    overhead, so the driver sets this profile in Windows Server 2012. As
    this is already the default in Windows 2008 R2, the driver doesn’t
    need to set it.



    ClosestProcessor:
    Default behavior is consistent

    ClosestProcessorStatic:
    No dynamic load-balancing - Distribute but don't load-balance at runtime.

    NUMAScaling:
    Assign RSS CPUs in a round robin basis across every NUMA node to enable applications that are running on NUMA servers to scale well.

    NUMAScalingStatic:
    RSS processor selection is the same as for NUMA scalability without dynamic load-balancing.

    ConservativeScaling:
    RSS uses as few processors as possible to sustain the load. This option helps reduce the number of interrupts.
    Last edited by n1kobg; Yesterday at 05:56 AM.

  4. #184
    Administrator Philip's Avatar
    Join Date
    May 1999
    Location
    Jacksonville, Florida, United States
    Posts
    9,980
    Blog Entries
    6
    I don't think you will see much difference changing that profile.

    Generally the RSS queue should be as big as the number of processor cores. It avoids packet reordering. With NUMA (Non-uniform memory access) processors get faster access to memory that is "close" to them. NUMA scaling is more important in scaling for large number of processors, or Virtual processors with Hyper-V. With only 4-8 cores it won't play a noticeable role.

    I would use a setting that does not use much processing. I imagine the default "ClosestProcessor" is fine, or something without dynamic scaling that would require more processing from the adapter drivers. Static scaling settings, or even the ConservativeScaling sound good. I wouldn't use the NUMAScaling unless in a multi-processor server environment with many memory banks and at least 2 processors/16 physical cores (+Hyperthreading), or something similar.

Similar Threads

  1. Replies: 10
    Last Post: 09-16-10, 10:02 AM
  2. TCP Optimizer version 3.0.3 released (64-bit Windows 7/2008 fix)
    By Philip in forum Broadband Tweaks Help
    Replies: 30
    Last Post: 09-06-10, 10:18 AM
  3. TCP Optimizer version 3.0.2 released (Windows 7/Vista support !)
    By Philip in forum Broadband Tweaks Help
    Replies: 18
    Last Post: 07-29-10, 03:07 PM
  4. TCP Optimizer version 3.0 released ! (Windows 7/Vista support)
    By Philip in forum Broadband Tweaks Help
    Replies: 37
    Last Post: 07-12-10, 10:27 AM
  5. Xfire has been updated to version .18
    By JawZ in forum Gaming
    Replies: 3
    Last Post: 07-23-04, 06:54 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •