Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 263 / 532

Chapter 10, Configuring the Server for Performance 263
Sizing Issues
Scaling of less than 25% would mean that the four-CPU server performs more
slowly than the one-CPU server. This does not happen in our testing, but the 4-
CPU static workload comes closest. Again, this is because the 100BaseT
network was close to saturation, so the server CPU was not the bottleneck. This
should not be regarded as a defect in Enterprise Server, but rather as a
limitation of the test environment.
Memory
As a baseline, Enterprise Server requires 64MB RAM. If you have multiple CPUs,
get at least 64MB per CPU. For example, if you have four CPUs, you should
install at least 256MB RAM for optimal performance. At high numbers of peak
concurrent users, also allow extra RAM for the additional threads. After the first
50 concurrent users, add an extra 512KB per peak concurrent user.
Drive Space
You need to have enough drive space for your OS, document tree, and log
files. In most cases 2GB total is sufficient.
Put the OS, swap/paging file, Enterprise Server logs, and document tree each
on separate hard drives. Thus, if your log files fill up the log drive, your OS will
not suffer. Also, you’ll be able to tell whether, for example, the OS paging file is
causing drive activity.
Your OS vendor may have specific recommendations for how much swap or
paging space you should allocate. Based on our testing, Enterprise Server 4.0
performs best with swap space equal to RAM, plus enough to map the
document tree.
Networking
For an Internet site, decide how many peak concurrent users you need the
server to handle, and multiply that number of users by the average request size
on your site. Your average request may include multiple documents. If you’re
not sure, try using your home page and all its associated subframes and
graphics.