Configuring HP SIM for Optimal Performance in Large Environments

16
Ensure
that
nothing
else
is
a
bottleneck
on
the
management
server,
client,
or
network.
If
your network
is
not
the
limiting
factor
in
your
setup,
then
a
fast
NIC
will
probably
not
help.
Ensure
that the
application,
CPUs,
memory,
and
disks
are
not
limiting
your
network
performance.
Try
a
test
case
of
your
management
server
and
clients
on
their
own
isolated
LAN
to
see
what
kind of
throughput
can
be
achieved.
Microsoft
Windows
Server
2008
performance
tuning
Even
though
most
performance
tuning
options
are
equally
applicable
to
Microsoft
Windows
2008,
there
are
additional
performance
aspects
to
consider
when
optimizing
your
Microsoft
Windows server.
CPU
configuration
Changing
the
CPU
speed,
the
CPU
cache
size,
or
the
number
of
CPUs
in
a
web
server
can
improve
performance
significantly.
Using
a
faster
CPU
or
one
with
a
larger
cache
always
improve
s
the
performance
of
a
web
server
with
a
CPU
bottleneck.
For
example,
on
web
servers
that
respond
to
a
significant
number
of
dynamic
requests
and
use
encryption,
increasing
the
number
of
CPUs,
CPU
speed,
or
CPU
cache
size
can
be
a
very
effective
way
to
increase
performance.
Even
though
HP
SIM
is
typically
not
CPU
bound,
other
system
components,
such
as
the
operating
system,
Microsoft
SQL
Server,
or
other
applications,
all
benefit
from
the
addition
of
another
processor,
improving
overall
system
performance.
However,
adding
CPU
resources
to
a
C
PU-limited
Web
server
sometimes
does
not
improve
performance.
If
you
do
not
see
much
performance
improvement
for
a
highly
dynamic
site
when
adding
CPU
resources,
the
problem
might
be
with
the
design
of
the
dynamic
content
or
web
application.
For
static
workloads,
the
CPU
is
unlikely
to
be
the
bottleneck;
the
usual
culprit
is
the
network.
Memory
Web
server
performance
is
very
sensitive
to
the
amount
of
memory
in
a
server.
For
example, Microsoft
Windows
2008
can
cache
high
demand
files
in
physical
memory.
By
caching
static
files
in memory,
the
server
can
process
requests
more
efficiently
since
disk
input/output
is
eliminated
(except for
logging).
For
the
best
performance,
a
web
server
should
have
enough
memory
to
hold
all
static files.
If
this
is
not
possible,
the
disk
subsystem
becomes
more
critical.
Systems Insight Manager
memory
requirements
There
are
three
main
processes
associated
with
Systems Insight Manager:
mxdomainmgr
mxdomainmgr
is
the
main
process
that
runs
Systems Insight Manager.
It
is
started
by
the
primary
Systems Insight Manager service
and is
responsible
for
initializing
and
managing
the
core
Systems
Insight Manager web
application,
partner
code,
and
so on.
This
service
runs
the
web
server
as
well
as
the
bulk
of
the
code
that
is
Systems Insight Manager.
It
is
not
unusual
to observe
mxdomainmgr
using
750
MB
or
more
of
memory.
Note
that
mxdomainmgr
runs
within
a
Java
Virtual
Machine
process,
which
is
restricted
to
the
maximum
amount
of
memory
available
to
any
single
process
in
Windows
Server
2008 32-bit,
namely,
approximately
1.6
GB.
This
restriction
is
because
32-bit
Windows
does
not
allow
any
single
process to
allocate
more
than
2
GB
of
memory.
The
JVM
heap
must
be
allocated
in
a
single
contiguous
block of
memory,
and
since
Windows
breaks
up
contiguous
memory
with
additional
libraries
and
so
on, the
JVM
never
utilizes
more
than
2
GB
of
memory.
Keep
this
in
mind
when
considering
system
RAM
upgrades;
though
SQL
Server
benefits
(as
will
other
concurrent
processes),
the
JVM
does
not
benefit.
Using Server 2008 64-bit allows unrestricted maximum Java VM virtual address size.
mxdtf