Current Position:Home > Multiple client hosting

Multiple client hosting

Update:11-30Source: network consolidation
Advertisement
I've been programming for WebLogic for some time now, and have recently
been asked to help solve a performance problem we've been seeing with one
of our production systems. Because I know diddly about configuring a
production system based on WebLogic, I'd really like a sanity check on
what we're doing.
We've got a 4 processor Sun with gobs of RAM (8GB, I believe) and hard
disk space, with fast network connections to separate machines for a web
server (and Tomcat) tier and Oracle database tier.
This machine is overkill for any one of the client organizations who
currently use the application we've developed, so we're hosting several of
them on the same machine. This is being done by running a separate
instance of WebLogic (currently 5.10 SP11, moving to 8.1 SP1 very soon) in
a separate JVM (currently 1.3.1_6, moving to 1.4.2 very soon).
Assuming that we have enough RAM and HD (which we certainly appear to
have), does anyone see anything wrong with this approach (separate JVM per
client)? Are we paying a large overhead price for going this way, instead
of trying to host all of the clients out of a single JVM instance?
-- Erik

The Best Answer

Advertisement
Hi Erik,
I think it's fine, if the applications don't use up the
resources available. But you said that you have
a performance problem - what kind of a problem?
Also - do you have monitoring data for this box,
like CPU, disk, memory, swap, network, database
utilization? Anything looking not-that-good?
Regards,
Slava Imeshev
"Erik Horstkotte" <[email protected]> wrote in message news:3f2f044d$[email protected]..
I've been programming for WebLogic for some time now, and have recently
been asked to help solve a performance problem we've been seeing with one
of our production systems. Because I know diddly about configuring a
production system based on WebLogic, I'd really like a sanity check on
what we're doing.
We've got a 4 processor Sun with gobs of RAM (8GB, I believe) and hard
disk space, with fast network connections to separate machines for a web
server (and Tomcat) tier and Oracle database tier.
This machine is overkill for any one of the client organizations who
currently use the application we've developed, so we're hosting several of
them on the same machine. This is being done by running a separate
instance of WebLogic (currently 5.10 SP11, moving to 8.1 SP1 very soon) in
a separate JVM (currently 1.3.1_6, moving to 1.4.2 very soon).
Assuming that we have enough RAM and HD (which we certainly appear to
have), does anyone see anything wrong with this approach (separate JVM per
client)? Are we paying a large overhead price for going this way, instead
of trying to host all of the clients out of a single JVM instance?
-- Erik