I have a project with a number of users editing attributes in a large module (30,000 objects) using Doors Web Access 9.6.1.1 I have not been able to find any guidance on whether setting the module up for sharable edit would be better or worse for DWA users, who are primarily in review mode, but occasionally go into editing mode. Anybody have an opinion on whether to set the module to level 4 sharing, or leave it whole (about 1200 sections at level 4) Can't find any meaningful description of how DWA is working against the module when editing. Does the interop use exclusive edit for the few seconds it takes to save an edit? Does it set up sharable edit for a minute, perform the save, and then undo that? I am having some reasonably serious performance issues, even after moving the whole installation to 9.6.1.1 with as little as 3 users logged in. Cliff Sadler BTI - Mon Apr 27 09:26:05 EDT 2015 |
Re: DWA and sharable edit If you plan to edit in DWA, then I believe setting up shared sections should make things quicker in DWA (while in edit mode). This will likely have to do with only the section containing the object for edit being reloaded (done to ensure that the data is up to date), rather than the whole module which would take more time. |
Re: DWA and sharable edit kourosh - Thu May 07 12:12:52 EDT 2015 If you plan to edit in DWA, then I believe setting up shared sections should make things quicker in DWA (while in edit mode). This will likely have to do with only the section containing the object for edit being reloaded (done to ensure that the data is up to date), rather than the whole module which would take more time. That would be my thinking, yet even with level 4 sharable edit in a reasonably normal module (~6000 objects), on a very fast network, my first edit of a single attribute took 16 seconds to save this morning. The next 5 or so took an average of 5 seconds. sure wish someone could point me to some technical theory of operation for DWA so I would know where to look next for performance improvements. I have a 4 processor 32 Gig 2008 Server R2 VM, with 4 interops set up. The desktop client edits are lightning fast, as expected.
|
Re: DWA and sharable edit Cliff Sadler BTI - Fri May 15 09:10:30 EDT 2015 That would be my thinking, yet even with level 4 sharable edit in a reasonably normal module (~6000 objects), on a very fast network, my first edit of a single attribute took 16 seconds to save this morning. The next 5 or so took an average of 5 seconds. sure wish someone could point me to some technical theory of operation for DWA so I would know where to look next for performance improvements. I have a 4 processor 32 Gig 2008 Server R2 VM, with 4 interops set up. The desktop client edits are lightning fast, as expected.
I recently did some installs of DWA and noticed that the IBM recommendation is to run four interops in parallel to one DOORS database server. Have you implemented this? |
Re: DWA and sharable edit Pekka_Makinen - Fri May 15 10:59:09 EDT 2015 I recently did some installs of DWA and noticed that the IBM recommendation is to run four interops in parallel to one DOORS database server. Have you implemented this? Yes, I have. refer to a white paper in developerWorks called Steps to scale load balancing in Rational DOORS Web Access by Lee Byrnes. Stay away from the -lightserver switch. http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI23625 If you can't find the paper let me know, and I'll send it to you.
|
Re: DWA and sharable edit Cliff Sadler BTI - Fri May 15 11:17:00 EDT 2015 Yes, I have. refer to a white paper in developerWorks called Steps to scale load balancing in Rational DOORS Web Access by Lee Byrnes. Stay away from the -lightserver switch. http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI23625 If you can't find the paper let me know, and I'll send it to you.
everything I have experienced with DWA (DOORS Lite) adds layers of translators and data type handoffs of the data all the way from user browser to apache server to IIS to interop doors client to doors database VS. the Client ->Server DOORS full richly functional tool. Soooo... that being said, and with the continued stray locks and slow performance even when you do the load balancing act with 4 interop servers (doors client running on the doors server)... throw in the stray locks issues and it just makes a DOORS DB Admin dizzy and miserable... I wish it weren't true... that seems like increased levels of trouble come deployment of DWA... I had fought my way thru the 2nd and 3rd versions of DWA... not sure if we will bring it along with our pending DOORS v9.3.0.5 Server with DWA into the DOORS v9.6.1.2 Server with DWA.... just really adds A LOT of needful attention to keep it limping along to anything near what the Client->Server tool can do... just sayin... gsdguy... |
Re: DWA and sharable edit gsdguy - Thu May 21 15:18:12 EDT 2015 everything I have experienced with DWA (DOORS Lite) adds layers of translators and data type handoffs of the data all the way from user browser to apache server to IIS to interop doors client to doors database VS. the Client ->Server DOORS full richly functional tool. Soooo... that being said, and with the continued stray locks and slow performance even when you do the load balancing act with 4 interop servers (doors client running on the doors server)... throw in the stray locks issues and it just makes a DOORS DB Admin dizzy and miserable... I wish it weren't true... that seems like increased levels of trouble come deployment of DWA... I had fought my way thru the 2nd and 3rd versions of DWA... not sure if we will bring it along with our pending DOORS v9.3.0.5 Server with DWA into the DOORS v9.6.1.2 Server with DWA.... just really adds A LOT of needful attention to keep it limping along to anything near what the Client->Server tool can do... just sayin... gsdguy... I can tell you that there is a WORLD of difference between 9.3.0.5 DWA and 9.6.1.1 A lot of things were completely rewritten around DWA and dbadmin to better support CLM interaction. Do not stop at 9.6.1.0 or anything below that. I have a 9.5.1 server implementation where a module save using the desktop client when affecting all objects takes about 30 minutes. On a 9.6.1.1 server and client, it takes about 30 seconds.
I accepted Kourosh's reply about sharable edit because that was the suggestion from Tech support on my ticket. Not sure it will play out to be the best thing, still testing. One module has 30,000 objects, which translated into 7,000 sharable edit sections. That should be interesting.
|
Re: DWA and sharable edit Cliff Sadler BTI - Fri May 22 09:11:31 EDT 2015 I can tell you that there is a WORLD of difference between 9.3.0.5 DWA and 9.6.1.1 A lot of things were completely rewritten around DWA and dbadmin to better support CLM interaction. Do not stop at 9.6.1.0 or anything below that. I have a 9.5.1 server implementation where a module save using the desktop client when affecting all objects takes about 30 minutes. On a 9.6.1.1 server and client, it takes about 30 seconds.
I accepted Kourosh's reply about sharable edit because that was the suggestion from Tech support on my ticket. Not sure it will play out to be the best thing, still testing. One module has 30,000 objects, which translated into 7,000 sharable edit sections. That should be interesting.
Thanks for the feedback... i am actually updating our DOORS to v9.6.1.2 server this weekend... and good luck with you large number of sharable edit sections... you do realize that is like the # 1 module performance hit due to it creates multiple versions of the module on the server and then manages control of all those sections.. just saying i hope you are not expecting much more than a similar performance as an old chevy chevette or ford pinto... lol ... :) gsdguy |
Re: DWA and sharable edit gsdguy - Fri May 22 09:20:11 EDT 2015 Thanks for the feedback... i am actually updating our DOORS to v9.6.1.2 server this weekend... and good luck with you large number of sharable edit sections... you do realize that is like the # 1 module performance hit due to it creates multiple versions of the module on the server and then manages control of all those sections.. just saying i hope you are not expecting much more than a similar performance as an old chevy chevette or ford pinto... lol ... :) gsdguy I definitely would recommend splitting a module with 30k objects into smaller modules. |