Article View: pl.comp.os.winnt
Article #409Re: Workstation czy Server!
From: Sergiusz Pawlowicz
Date: Sat, 30 Nov 1996 19:02
Date: Sat, 30 Nov 1996 19:02
187 lines
11025 bytes
11025 bytes
-----BEGIN PGP SIGNED MESSAGE-----
Bronislaw Kozicki <bronek@wpi.com.pl> wrote:
: Zdecydowanie nie masz racji. Przeczytaj sobie
: <http://www.microsoft.com/kb/articles/q129/5/93.htm>
: zanim znowu cos na ten temat palniesz.
Szanowni Panstwo! Przeczytalem powyzszy artykul kilkukrotnie.
Nadal mi sie wydaje, ze NT Server niczym sie nie rozni od NT Workstation, jesli
chodzi o system operacyjny (a nie dodatkowe mozliwosci, ktore mozna wlaczyc).
Czyli nie ma mowy o optymalizacji, o jakichkolwiek _roznicach_, bo to jest po
prostu _to samo_. Poza oczywiscie wspomnianymi juz wielokrotnie na liscie
ograniczeniami ponad 10 polaczen "inbound" - to po prostu wymusza na
uzytkownikach zakup znacznie drozszego produktu, jakim jest server, zamiast
stacji roboczej, ktora do serwowania by sie swietnie nadawala.
Prosze uwaznie przeczytac pierwsza wyliczanke, ktora pozornie zawiera roznice
pomiedzy serwerem a workstation, ale na koncu mowi, ze workstation uzywana jako
server dziala tak samo jak server 8:)
Bo reszta argumentow jest smieszna. VDM? A co szkodzi, zeby sie zaladowalo na
zyczenie? Chyba nawet lepiej dla workstation? Watki? Jak mozna optymalizowac
watki dla programow pracujacych na serwerze aplikacji - to znaczy czym ta
optymalizacja rozni sie od optymalizacji watkow programu po prostu
uruchamianego na stacji workstation?
Ale moze nie znam angielskiego i sie myle? Nic nie rozumiem?
Dlatego:
Gdyby ktos znalazl jeszcze troche czasu na nasza dyskusje i po przeczytaniu
artykulu polecanego przez p. Bronislawa Kozickiego, ktory zalaczam ponizej,
powiedzial, czy server bez uaktywnionej sieci rozni sie czymkolwiek od
workstation czy tez nie?
- ---------
Windows NT Workstation and Server Optimized For
Different Role
Article ID: Q129593
Creation Date: 30-APR-1995
Revision Date: 03-SEP-1996
The information in this article applies to:
o Microsoft Windows NT Workstation version 3.5
o Microsoft Windows NT Server version 3.5
o Microsoft Windows NT Server version 4.0
o Microsoft Windows NT Workstation version 4.0
SUMMARY
This article discusses the roles for which Windows
NT Workstation and Windows NT Server are optimized.
MORE INFORMATION
Microsoft optimized both Windows NT Workstation and
Windows NT Server to better serve their intended
purposes. Windows NT Workstation is a great
corporate client for users who need the power,
scalability, fault tolerance, or security it
offers. Windows NT Server is a powerful server
environment for customers who want to leverage its
application server, file and print services, or
remote access capabilities. The following
optimizations were made in Windows NT version 3.5:
o The write-throttling mechanism (the point at
which dirty data is flushed to disk) is
implemented differently for the Windows NT
Server and Windows NT Workstation. This allows
the server to handle server-like loads and the
workstation to handle desktop-like tasks.
o The internal code that provides the Windows NT
Server server functionality (SRV.SYS) is less
pagable. This leads to better response times
under heavy server-type loads.
o Under Windows NT Workstation, the Windows NT
Virtual DOS Machine (VDM) is pre-loaded for
improved application startup times. Windows NT
Server does not pre-load the VDM, but instead
optimizes server file operations.
o Windows NT Workstation and Windows NT Server
use a different number of system worker
threads and threads for blocking operations.
Windows NT Server is optimized for fast server
type I/O operations and Windows NT Workstation
is optimized for desktop applications.
o Windows NT Server can be optimized for file
and print server performance or application
server performance, allowing you to tune it
for maximum throughput depending on the type
of server usage. Windows NT Workstation does
not have this feature. Internal testing has
also shown that Windows NT Workstation
performs about the same as Windows NT Server
up to approximately 10 different, simultaneous
inbound user connections. This enables Windows
NT Workstation to function well in a small
peer environment. Windows NT Server is the
correct choice if you want to deploy a server
in a larger environment or want to scale your
network in the future.
These optimizations changed the performance of
Windows NT Workstation when used as a server. As a
result, peer networking is still supported for
basic connectivity between users on a network. You
can still make unlimited outbound connections to
server resources. However, Windows NT Workstation
now supports a maximum of 10 simultaneous inbound
connections. Our research has shown that systems
with this many connections are almost always being
used as dedicated file, print and/or application
servers.
While Windows NT Server can certainly provide
excellent file and print services, it can also be
used extensively as an application server platform
for database and other services. The Windows NT
Server file and print capabilities can be
selectively implemented.
Windows NT Server includes the following
capabilities not available on Windows NT
Workstation:
o Dynamic Host Configuration Protocol (DHCP)
server service (Both Windows NT Workstation
and Server have DHCP Protocol)
o Windows Internet Naming Service (WINS)
o Single network logon
o Data protection features (disk striping, RAID
5, disk mirroring)
o Remote Access Server service can handle 255
concurrent incoming calls (Windows NT
Workstation limited to one incoming call)
o Gateway Services for NetWare(GSNW)
o Gateway to NetWare file and print resources
for MS network clients
o Services for Macintosh (allows Macintosh
clients to access file and print resources on
the Windows NT Server, and allows Microsoft
network and Macintosh clients to access
AppleTalk-based printers)
o Netlogon request authentication (for running
logon scripts)
o Account lockout security
o Network Client Administrator
o Administrative tools (Server Manager, User
Manager for Domains)
o Support for remote boot of diskless
workstations (RPL)
Because Windows NT Server is optimized as a server
platform, it is required to run Microsoft
BackOffice products (Systems Management Server, SNA
Server, SQL Server, and the upcoming Exchange
Server).
Microsoft recommends Windows NT Workstation as a
desktop operating system and Windows NT Server as a
server operating system for server applications.
This provides you an environment that is
architecturally very clean, since both the desktop
and server are running the same operating system,
and have the same APIs, etc.
ę1996 Microsoft Corporation
- --ser
PS Przepraszam za poprzedni list w watku, ktory oczywiscie mial pojsc prywatna
poczta do p. Bronislawa Kozickiego, a nie na liste. Bardzzo mi glupio z tego
powodu.
- --s
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
iQCVAwUBMqCE0DS5h5vvlgEFAQH/jwP/UPD5jGI7zw594BDug7xRCgReuMqM5KuU
hLcxelvoNGCIw4BQKSQoBpBSg0SVKikC5jVCgKp2FDN6HjGxwaVsE11MA19LiF1U
SOKNGOwfxGoX0p2hg3J4RYym121LxmXAq02DOCeB/iCOeKvGxGd42Ao7KXQgIvwA
YEz0kIemk7Y=
=GQMh
-----END PGP SIGNATURE-----
Technical Details
Message-ID:
<57q0cg$bu4@sun1000.pwr.wroc.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!pingwin.icm.edu.pl!news.icm.edu.pl!ict.pwr.wroc.pl!pwr.wroc.pl!serek.arch.pwr.wroc.pl!not-for-mailReferences:
<01BBDECE.43E793E0@spring95>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!pingwin.icm.edu.pl!news.icm.edu.pl!ict.pwr.wroc.pl!pwr.wroc.pl!serek.arch.pwr.wroc.pl!not-for-mail From: Sergiusz Pawlowicz <ser@serek.arch.pwr.wroc.pl> Newsgroups: pl.comp.os.winnt Subject: Re: Workstation czy Server! Date: 30 Nov 1996 19:02:40 GMT Organization: Technical Univeristy of Wroclaw Lines: 187 Message-ID: <57q0cg$bu4@sun1000.pwr.wroc.pl> References: <01BBDECE.43E793E0@spring95> Reply-To: ser@arch.pwr.wroc.pl NNTP-Posting-Host: serek.arch.pwr.wroc.pl Mime-Version: 1.0 X-Newsreader: TIN [UNIX 1.3 unoff BETA release 961109] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit