We recently moved Livelink to two new servers and have been experiencing severe performance problems on the front-end web server where it maxes out at 100% CPU for certain functions. For the old servers, we had two physical machines, both with four 3065mhz processors. For the new, we have a similar back end server with four 2694mhz processors. The front end however is a virtual server with only one 2694mhz processor. Also, since it is virtual, it has a 50% guarantee, which is about 1/8 of what I previously had. Could this be my problem?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Performance problem on new machine
- Thread starter pjb
- Start date
Syntergy
Programmer
- Jun 2, 2004
- 52
If the server maxes out at 100% cpu it is probably not a hardware configuration issue. We have done a lot of work in performance analysis and typically these types of problems come down to one of three things:
1. Software Issue - an example is the Recycle Bin module caused severe CPU impact because it made execessive calls to the database. Removing the module cleared up all the performance problems.
2. Architecture - this is a complicated subject but the way you architect your hardware and software can make a big difference. A common problem is running Livelink index processes on the same server that is running the Livelink service. That are other issues including thread contention, virus scanning conflicts, load balancer issues, etc. Swapping out a sever with less CPU may have exposed an issue in these areas.
3. Tunning problems. This can include the database performance, number of threads allocated per Livelink server, opentext.ini configuration settings, etc.
Turning on logging and analyzing your thread.out files for transaction times is a good place to start. You can also look at your database connect logs to see if there are database issues. You can look at your indexing processes to see if they are sucking up CPU periodically. If nothing is obvious from looking at these things you may need to get some expert help.
1. Software Issue - an example is the Recycle Bin module caused severe CPU impact because it made execessive calls to the database. Removing the module cleared up all the performance problems.
2. Architecture - this is a complicated subject but the way you architect your hardware and software can make a big difference. A common problem is running Livelink index processes on the same server that is running the Livelink service. That are other issues including thread contention, virus scanning conflicts, load balancer issues, etc. Swapping out a sever with less CPU may have exposed an issue in these areas.
3. Tunning problems. This can include the database performance, number of threads allocated per Livelink server, opentext.ini configuration settings, etc.
Turning on logging and analyzing your thread.out files for transaction times is a good place to start. You can also look at your database connect logs to see if there are database issues. You can look at your indexing processes to see if they are sucking up CPU periodically. If nothing is obvious from looking at these things you may need to get some expert help.
- Thread starter
- #3
I did open a ticket with Opentext. They had me turn on logging,isolate the function and send them the results. Here is the reply:
The edit of the user takes 106 seconds. Three seconds of that is in the database or Livelink. The rest of that time is spent waiting for the OS to catch up. Basically, what I am seeing indicates that your resources simply are ot adequate to keep up with what Livelink is trying to do.
The edit of the user takes 106 seconds. Three seconds of that is in the database or Livelink. The rest of that time is spent waiting for the OS to catch up. Basically, what I am seeing indicates that your resources simply are ot adequate to keep up with what Livelink is trying to do.
- Status
Similar threads
- Locked
- Question