mitek
asked on
BEA Weblogic 8.1 server on a multi-cpu machine
We're planning for a deployment of WL81 on a Sun (sunfire) box with 6 CPUs. Initially this box will host the whole production deployment, including a Sybase ASE database server, WL server and possibly some other services (such as messaging, etc). Later on, we plan to migrate some things off to other boxes.
Initially, we plan to buy a single-cpu "WL Advantage" license for a WL81 server to be deployed on this box.
Question: what is the behavior of a WL server running with one-cpu license on a multi-cpu machine -- does it pin itself to one CPU only or uses all available resources regardless of its license ? In other words, does the (single-cpu) license affect the behavior of the server by pinning it to one cpu or not ? If not, is it possible to achieve and how ?
I need an answer of someone who have actually dealt with this issue and installed/benchmarked the weblogic server on a multi-cpu machines (any WL admins out there?) and can explain exactly what happens when WL runs on multiple CPUs and how licensing affects that; reference articles (like, from http://e-docs.bea.com/wls/docs81) proving the point will also be very helpful. Any input will be appreciated.
Thank you.
Initially, we plan to buy a single-cpu "WL Advantage" license for a WL81 server to be deployed on this box.
Question: what is the behavior of a WL server running with one-cpu license on a multi-cpu machine -- does it pin itself to one CPU only or uses all available resources regardless of its license ? In other words, does the (single-cpu) license affect the behavior of the server by pinning it to one cpu or not ? If not, is it possible to achieve and how ?
I need an answer of someone who have actually dealt with this issue and installed/benchmarked the weblogic server on a multi-cpu machines (any WL admins out there?) and can explain exactly what happens when WL runs on multiple CPUs and how licensing affects that; reference articles (like, from http://e-docs.bea.com/wls/docs81) proving the point will also be very helpful. Any input will be appreciated.
Thank you.
Even if you are running WL server with evaluation license, it's utilizing all of your CPU's.
ASKER
> I think what single CPU really mean is that you can install your sever only on one machine and run it on IP's what license is registered with.
That's a very valuable input -- so, you're saying that the license is really ip-bound, not cpu-bound ? Are there any proofs (online documents, links to discussion groups, etc), to back up this statement ? (I could do some research myself, but someone who's WL admin and works with WLS on daily basis would do it much better -- that's why this question is posted here)
> ran single CPU wls 81 licenses on sun servers with 2, 4 and 6 CPU's and it was always utilizing all of the CPU's.
Did you have a real, (that is, purchased) single-cpu license (~10-17 K$) or a free evaluation license ?
> Even if you are running WL server with evaluation license, it's utilizing all of your CPU's.
This one I have no even doubts about. Evaluation license is NOT restricted by CPUs, it just collects client's IP addresses, and when it counts 5 of them it will refuse to serve anybody else except those first 5 clients. Quite effective -- and no need to limit CPU utilization.
Again -- message to everybody -- please, feel free to leave your 2c on the subject -- the points will be split, if necessary.
That's a very valuable input -- so, you're saying that the license is really ip-bound, not cpu-bound ? Are there any proofs (online documents, links to discussion groups, etc), to back up this statement ? (I could do some research myself, but someone who's WL admin and works with WLS on daily basis would do it much better -- that's why this question is posted here)
> ran single CPU wls 81 licenses on sun servers with 2, 4 and 6 CPU's and it was always utilizing all of the CPU's.
Did you have a real, (that is, purchased) single-cpu license (~10-17 K$) or a free evaluation license ?
> Even if you are running WL server with evaluation license, it's utilizing all of your CPU's.
This one I have no even doubts about. Evaluation license is NOT restricted by CPUs, it just collects client's IP addresses, and when it counts 5 of them it will refuse to serve anybody else except those first 5 clients. Quite effective -- and no need to limit CPU utilization.
Again -- message to everybody -- please, feel free to leave your 2c on the subject -- the points will be split, if necessary.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
> And right now I am monitoring one of the Sun servers, running prstat command and watching WL 8.1 server java process and I can watch how process randomly running on different CPU's. and I am using single CPU license.
fair enough.
just one last question -- what is prstat and how it is used ? What it's capable of ? Is it a part of OS or some kind of 3rd party tool ?
fair enough.
just one last question -- what is prstat and how it is used ? What it's capable of ? Is it a part of OS or some kind of 3rd party tool ?
Yes, /usr/bin/prstat is a standard tool for Solaris , if you just run "prstat" command without any switches, it will display different information about processes ( PID, memory and CPU utilization, Status ( "sleep" or "CPU#" on which process is currently running, )).Usually prstat sort processes by CPU utilization.
If you want to monitor some specific process, you can run
"prstat -p %process ID%". See "man prstat" for more information.
Also, if you'd like to bind specific process to specific CPU, you can use "pbind" command, but usually you don't need this.
Z.
If you want to monitor some specific process, you can run
"prstat -p %process ID%". See "man prstat" for more information.
Also, if you'd like to bind specific process to specific CPU, you can use "pbind" command, but usually you don't need this.
Z.
I think what single CPU really mean is that you can install your sever only on one machine and run it on IP's what license is registered with.
I ran single CPU wls 81 licenses on sun servers with 2, 4 and 6 CPU's and it was always utilizing all of the CPU's.
Zhenek.