Hardware Requirements for SAProuter-CSDN博客

本文链接：https://blog.csdn.net/xiegh2014/article/details/47776681

SAProuter Architecture andRequirement Profile

Since the work ofthe SAProuter (also with SNC) is mainly I/O-based (input/output), you do notrequire any especially powerful CPU.

The workloadhandled by the SAProuter is determined by the number of openconnections.

If over 800connections have to be maintained, we recommend that you start new SAProuterprocesses withOption -Y<n>. This distributes the load across several processes and reducesthe risk of any problem occurring(if a problem does occur, it never affects all the open connections.) The ruleof thumb is 1 SAProuter for every 500 connections.

Alternatively tooption -Y you can also set ascript that monitors the SAProuter process and restarts the SAProuter (softshutdown withOption -p, thenrestart), as soon as a certain number of connections is exceeded, or when themessageMaximum number ofclients reached is issued for the first time.

Since the SAProuterprocess is running in one thread (single threaded) and is often busy with I/Ocalls or with host name resolutions, a computer with one CPU manages well withseveral SAProuter processes running in parallel.

Recommended Hardware

For an SAProuterwith 3000 parallel connections between SAP GUIs and application servers,transferring an average volume of data, a small number of file downloads anduploads (approximately 8kB data transfer in both directions per connection andper 10 seconds), we recommend:

● Quick networkadapter (very important)

● 2 hyper-threading(HTT) CPUs with 2GHz tact frequency

● 512 MBRAM

● 50 MB free space onthe hard drive

Background

For 3000 users weestimate six SAProuter processes (set Option -C<clients> to 1000).

Each of theseprocesses requires 4.5 MB of memory, and 9% of a two-way HTT 3 GHz CPU, if youassume one third of the CPU workload is for the users and two thirds for thesystem. The six SAProuter processes together require approximately 30 MB and55% of the CPU.

Sometimes it takesa few seconds to determine the host name from the IP address (reverse lookup),and during this time the process is blocked. The cause is usually an error inthe DNS configuration. Users will notice these delays particularly if theworkload on the SAProuter is large. Use Option -D, toprevent this happening.