Performance problem or what?

[steen.jensen]

We have about 25 users of Sparx EA 13.52 with MS-SQL repository and Windows 7 workstations.
Some users within the company have a separate Active Directory then the rest of the users for Windows Domain logon.

Within same network, users from the secondary AD have much slower responses for EA actions.
Primary users have <1 sek response when moving an object in a diagram.
Secoondare user (Separate AD) have about 5 sek delay for same action (Same, network, object, diagram and repository)

We are using EA Security with SQL user & Pw (No sync or connection to Active Directory för EA autentication)

Any one out there having seen this before??

[Geert Bellekens]

I haven't seen any differences with regards to a separate AD group, but in almost all such cases the culprit was the network.

In one particular case we had users that were still connected tot he database using their Wifi instead the the network cable.
Disabling Wifi when plugged in via the cable resolved their performance issues.

Geert

[Sunshine]

If everything is the same bar the AD then it kind of points to that. Maybe AD is involved in authorising each request to the DB and one AD is slower at responding. Not sure how it all works under the hood but may be AD is involved in validating security tokens on each request to the DB.  You might be able to find out some kind of message sequence diagram via google to help understand how DB requests and AD interact for authorisation.

Networks can also be set up to give different qualities of services and that might be dependent on which AD users are on.

If you want an approach to problem solving look up Kepner Tregoe. It helps to work through the logic and isolate root cause. I've used it a lot over the last 25 years and it was really useful.

[Glassboy]

It seems like you are operating across a WAN, you really need to use the WAN accelerator.  As well as decreasing the chatter across the wire it's going to simplify the authentication across domains.

[Paolo F Cantoni]

If everything is the same bar the AD then it kind of points to that. Maybe the AD is involved in authorising each request to the DB and one AD is slower at responding. Not sure how it all works under the hood but maybe AD is involved in validating security tokens on each request to the DB.  You might be able to find out some kind of message sequence diagram via google to help understand how DB requests and AD interact for authorisation.

Networks can also be set up to give different qualities of services and that might be dependent on which AD users are on.

If you want an approach to problem-solving look up Kepner Tregoe. It helps to work through the logic and isolate the root cause. I've used it a lot over the last 25 years and it was really useful.

Kepner Tregoe - Blast from the past!

Paolo