![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Hardware Recommendations Topic Summary: Created On: 18-Aug-2003 18:47 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello there,
We are currently running DOORS 6.0R1 on a 800MHz machine with 256 megs of memory. The "minimal requirements" recommended were much lower than this but the machine is now crawling as the database gets larger. From our testing, it seems as if DOORS is more processor dependent while not consuming as much memory. Does anyone have any success loading doors with optimal performance on certain server specifications? Would you mind recommending some server specs as well as confirm the particular resources (processor, memory, ...) that DOORS seems to be more dependent on? thank you. |
|
![]() |
|
![]() |
|
You may want to specify the specs of the server, the specs of the typical clients, and whether client software is loaded locally ("Typical Client") or on the server ("Workstation").
You probably also want to run a DOS window on the client and check the "ping" times between client and server. - Louie |
|
![]() |
|
![]() |
|
Hi,
I'm not sure if I'm wide of the mark here but if you're actively running a client on the same host as the server, then there's a good chance that you may be suffering from memory leakage. I've seen this happen where a user had access to the client that was installed on the same production host as the DOORS DB server - this user was quite active and over a period of time, the performance of the DB server host declined - After a power restart, the performance of the host was back to normal but declined again over a 2 week period. We discovered via the Win2000 Task Manager that physical memory allocation was much much higher than expected - another power restart and daily observations revealed physical memory creepage. Once the user was asked not use the production host for client access, the problem went away. The DOORS DXL scripting language has a history of memory leakage, even if you're not actively executing DXL scripts, the client itself uses DXL to execute some client functions so memory leakage may compund over a period of time. Users operating a DOORS client on their own desktop often don't encounter this leakage problem because they restart their PC's on a daily basis, where-as production hosts are typically restarted on an irregular basis. Hope this helps. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
Telelogic DOORS
» Administration
»
Hardware Recommendations
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.