NetScaler is a highly scalable TCP stack that is built to take care of various network conditions and different types of clients / servers. In any communication channel state on TCP what makes the difference is the client-side stack of server-side stack, intermediaries and network conditions. Beyond these critical aspects of the application layer and the impacts with the nature of the application, the size of the request / response and how it makes the difference of the TCP connection characteristics.
In most cases what we have in default TCP holds well, but if you know more about your application, client / server and network conditions, you can use one of the built-in profiles TCP. These profiles have refined TCP TCP parameters that are significantly different in terms of lower latency, faster response time and better use of bandwidth in the given application and network environment. NetScaler can also create your own profiles with TCP TCP these basic parameters that optimize the TCP stack for your deployment. TCP profile can be used globally, which has a large impact system and it can also be used by vserver and service to locate the impact. This means that you can have virtual TCP stacks for several vservers and services within NetScaler, is not really interesting?
The integrated profiles for common deployment scenarios based on different characteristics of the network and applications. Let us understand the supplied integrated in the TCP profiles:
- Nstcp_default_profile
- impact system
- profile by default TCP globally
- Any change impacts the TCP global parameters
- Does not need to be related to explicit vserver / services
- Gets redefined by the level profiles vserver / Service
- Nstcp_default_tcp_lfp
- This profile is recommended to be used in networks
- High bandwidth
- packet loss Low
- High Time Round-Trip (RTT)
- Suitable for Type WAN environmen
- Useful when there is dedicated bandwidth
- when using the company through WAN
- This profile is recommended to be used in networks
- Nstcp_default_tcp_lnp
- This profile is recommended to be used in networks with
- Low bandwidth
- high loss packet
- High round trip Time (RTT)
- Suitable for WAN type of environmen
- Useful bandwidth when it is restricted
- use cases online through WAN bandwidth divided
- This profile is recommended to be used in networks with
- Nstcp_default_tcp_lan
- This profile is suitable for LAN
- mostly for use with servers in the same data center
- useful when access is limited to the same LAN
- Nstcp_default_tcp_lfp_thin_stream
- Similar to Nstcp_default_tcp_lfp
- Tuned for small speed packet
- Nstcp_default_tcp_lnp_thin_stream
- Similar to Nstcp_default_tcp_lnp
- Tuned for small packet flow
- Nstcp_default_tcp_lan_thin_stream
- similar to Nstcp_default_tcp_lap
- Tuned for small packets flow
- Nstcp_default_tcp_interactive_stream
- This profile is recommended for use with
- Chatty applications like telnet
- application virtualization environment
- Small package and fast applications on the basis of comments
- should function with different types of networks
- This profile is recommended for use with
- Nstcp_internal_apps
- This profile is recommended only for internal services
- should not be used for any other network service
in most case you will see that one of these profiles will suit your needs. NetScaler also supports the creation of TCP profiles defined by the user and you can define your own profile based optimization settings you want. It gets more interesting when you can customize all settings in the TCP profile. Well, we'll keep that excitement to the next blog ... 
0 Komentar