Hello Seung,
It is hard to determine performance issues without providing a lot more information. I"m surprised you got Build Forge to run at all on a non-supported operating system (what localization of Windows is BF running on in your screen examples?).
Large amount of log output from build steps can put a strain on the database, as all that output gets written to the DB. Also the amount of threading can impact the performance on the management console if that is also where the database resides. 1GB RAM on the management console is not a lot of memory for a production Build Forge server- is this for test/evaluation purposes? Remember this machine is running a web server (Apache), a database (DB2), and the Rational Licensing Manager (FlexLM) along with a lot of Build Forge processes (bf*.exe). Also what else is installed on this server? I see from the process output there is VM Ware. You should have at least 2GB RAM on a Build Forge production server if all the components are running on there, including the database.
We do not have a lot of experience tuning the DB2 database yet, as this was a new DB platform we added support for in June 2006. If your customer has access to MySQL and is willing to manually install it, that might help compare database performance to see if it improves or not.
I did a quick Google search of "db2syscs.exe CPU" and this website has a few users who have posted a similar question that you did regarding this process taking a lot of CPU time and some suggestions to address it: http://www.lazydba.com/ (click on "DB2 & UDB Archive" and type in "db2syscs.exe CPU" to search).
Doug
It is hard to determine performance issues without providing a lot more information. I"m surprised you got Build Forge to run at all on a non-supported operating system (what localization of Windows is BF running on in your screen examples?).
Large amount of log output from build steps can put a strain on the database, as all that output gets written to the DB. Also the amount of threading can impact the performance on the management console if that is also where the database resides. 1GB RAM on the management console is not a lot of memory for a production Build Forge server- is this for test/evaluation purposes? Remember this machine is running a web server (Apache), a database (DB2), and the Rational Licensing Manager (FlexLM) along with a lot of Build Forge processes (bf*.exe). Also what else is installed on this server? I see from the process output there is VM Ware. You should have at least 2GB RAM on a Build Forge production server if all the components are running on there, including the database.
We do not have a lot of experience tuning the DB2 database yet, as this was a new DB platform we added support for in June 2006. If your customer has access to MySQL and is willing to manually install it, that might help compare database performance to see if it improves or not.
I did a quick Google search of "db2syscs.exe CPU" and this website has a few users who have posted a similar question that you did regarding this process taking a lot of CPU time and some suggestions to address it: http://www.lazydba.com/ (click on "DB2 & UDB Archive" and type in "db2syscs.exe CPU" to search).
Doug
이 글은 스프링노트에서 작성되었습니다.
