![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS performance Topic Summary: Howto speed up module opening performance Created On: 4-Dec-2007 20:47 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I am receiving complaints that it takes awhile to open modules. The delay appears to be getting worse (does not appear to be tied to large history data). Are there command line switches, etc. that can enable/disable features or dxl scripts that can be used to gather data on parameters (e.g. timestamp, open module, timestamp again upon open finished; along with recording cpu and memory usage). this way I could run a batch at points throughout the day to gather data. I see three places where bottle necks can occur: 1. server, 2. client, 3. netowrk. Is there anyway I can gather data, and/or try tweaking paramters (cache settings, etc.)? Has anyone resolved such issues, or know where I might need to look? I sent to this forum in the event DXL's can be used ifor resolution, please advise if I should send to other forums as well. Thanks very much, --Greg |
|
![]() |
|
![]() |
|
1) If not required, turn off history for links. Its a checkbox in the module properties window.
2) Don't have any Layout DXL columns in your standard view. Same with Attribute DXL. It has to be calculated and thus, can take a while depending on how much processing has to be done. Also, if you need to have it, make sure to optimize the code, don't just stick with the standard Analysis Wizard code. There's a lot of unused variables in that code, and you can convert the strings to buffers which can be deleted. 3) Baseline often if your users are creating a large amount of history. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
I was not aware of the first item. I will try that. However, I forgot to state in my original post, that the performance varies throughout the day.
|
|
![]() |
|
![]() |
|
Yes, the mostly likely cause of excessive module load times for certain modules is attribute or layout DXL in the default view; where this dxl traverses links and opens up lots of other modules. Yes, the default module view should not contain any such attr or layouts. Users should not define a default-user view that has attr or layout dxl in it either.
And, of course, lets not forget about attr or layout dxl in the default view of this module's link-partners, which are opened invisibly. The most likely cause of consistent long module load times is the network. Without a doubt, modern greased-lightening computers with huge memory can handle DOORS work, the network is rouitinely the cause of delays. This situation is very easy to diagnose: see if module load times drastically improve during off hours. Just be sure your test is the same, specifically the first thing you do when you start DOORS is to open the module. You can also 'ping' the server to see how far away it is from your client: open a DOS command windows (its got a black icon) and type "ping <server>", where <server> is either the IP address or the alias of your DOORS data server. e.g. ping 123.45.67.890 We are getting 28ms per attempt here and I think that's tolerable. 10ms -15ms should be attainable, unless you are on earth and the servers have been installed on Mars, like here. Well, actually they were installed on Venus by the Martians, but I digress.... I have a nagging memory that 40ms is the threshold between 'annoyingly' and 'intolerably' slow. I notice when I ping my own computer I get 1ms delays. I notice when I ping a local server I get 2ms delays. - Louie |
|
![]() |
|
![]() |
|
Another thing depending on how your company uses DOORS is to watch whats being imported. If you import technical documents, be careful. If an image was copied and pasted into Word, the image might be resized to fit in the document, but its still actually there in its full size which can be quite huge. DOORS doesn't like 8MB technical drawings to be put into objects. So be careful. If you do bring in technical documents from Word, check the image sizes. If you have an extremely large image(either in resolution or file size), resize the image to an 800x600 or 1024x768 JPG and put that into DOORs. If your users need to see the full one, they can always go to the actual document.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Thanks all for the input. I think the responses will lead to an answer. I will reply back with the resolution as I try the suggestions.
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DOORS performance
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.