Performance

Uldis

Are there any known performance problems with usign Connected Workspaces (Business Workspaces)?

What to be aware of? Amount of roles? Any limitations?

There was something long time ago if I remember correctly..

Uldis

Find more posts tagged with

Connected Workspaces

Comments

Nizar Ghazal

There were some problems with ECMLink back in the CS 10.0 days, wherein a browse to the container could cause quite a bit of slowdown due to that license check callback. We've addressed these sorts of big ticket items, a long time ago.

In modern versions?

I don't recall any real performance problems, really (I can't speak for anything except xECM for SAP), just that when you're using the asynchronous queue for workspace creation, you need to basically benchmark it for your production systems.

Only have as many requests at a time, as your receiving front-ends, and servicing database backend, can handle. I think our PS org has likely done this sort of tuning, before, for customers.

It's something that requires some testing and a good understanding of the throughput of one's own environment.

I can't recall, off the top-of-my-head, but we also had some best practice recommendations concerning roles/policies from SAP, and I believe we discouraged the use of many policies, once upon a time.

I'm sure it would be in the installation/administration guide, if you peruse it.

One more thing, said documentation will sometimes have little notes about certain configurations, or compatibility for certain module combos (depending on your setup, you CANNOT install some of the modules included in the connected workspace/template workspace bundle), please make sure when installing/setting up your xECM instance, that extra care is taken so that all things we put in the docs are carefully considered. By-and-large, most performance issues I've ever seen, are due to misconfiguration.

Thanks.

Uldis

Thank you!

We're currently thinking about just using Connected Workspaces (decoupled from the leading APP).

How is the security checked for a normal user is when you enter a folder?

1) 100 Connected Workspaces (each has 3 roles)

2) 100 standard folders (each has 3 groups in the ACL)

Nizar Ghazal

It's been a while since I've looked at the specifics, but I believe the process is basically like this:

First, folders, as it has the core basics. Administrators bypass permissions checks, so they will always access things quicker than regular users.

For a given depth, you will have see/see content permissions checked for the given account, and we will draw out various promoted actions depending on what particular permissions set you have, while being cognizant of usage privs. If you have certain object types that a user is not permitted to edit, but has permissions to, they will be able to see it, but not fully interact with it (ex: LiveReport). The page is then fully drawn, optionally paginating the number of nodes, therein.

If you're browsing a business workspace or a similar sort of container, depending on your configuration, the above will first happen, and then, in a call-back, there will be a check against the mapping or policy you have implemented that will determine whether a user has access to each component of the workspace, itself. This is where your policy setup is kind of important to carefully consider, you wouldn't want a very large number of rules that must be exhaustively checked, each time.

My memory is a bit rusty, but I believe there are also relational workspace components, too, to consider: there will be related workspaces that can be searched (this was known as the location modifier component, if I recall). Based on your permissions to related workspaces, there will be some checks, performed here, too.

Basically, when you're browsing regular folders in Content Server, it's relatively straight-forward, but with workspaces, there is a lot more that can happen on the back-end, depending on the kind of workspace, its configuration, related workspaces, your user rights, etc. Which is why I think it's something, when one is architecting the workspace templates, and mappings, for a future production environment, a lot of careful planning has to go into it.

I hope that helps you.

Hans Stoop

If you want to use roles that are similar to the roles that are used by projects and template workspaces then you run in similar issues.

Connected workspaces have more advanced mechanism to prevent possible issues. Most noteworthy is the group mapping mechanism where you can assign groups based on attribute values. In that case you don’t have to assign the users to the roles.

Group assignment support multiple attributes and multi-valued attributes. Also attribute changes are supported.

Both mechanisms can also be merged. Roles should only be used when they are really different for every workspace. For example when you have an employee workspace it makes sense to have a role for the employee to access its own workspace but the HR employees should be given access based on the group mapping.

Hans

On 19. Nov 2018, at 15:41, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

eLink : Performance
Performance Posted by uldis@contesto.no (Šilovs, Uldis) On 11/19/2018 09:39 AM

Thank you!We're currently thinking about just using Connected Workspaces (decoupled from the leading APP). How is the security checked for a normal user is when you enter a folder?1) 100 Connected Workspaces (each has 3 roles)2) 100 standard folders (each has 3 groups in the ACL)
[To post a comment, use the normal reply function]
Topic: Performance
Forum: Content Server Development Forum
Content Server: My Support

Uldis

ThanksAlthough I still dont get answer whether there are known performance issues with Connected Workspaces? If there is a performance impact (when using multiple roles) compared to folders, why OT keeps promoting it?> On 19 Nov 2018, at 22:50, eLink Entry: Content Server Development Forum wrote:> > Re Performance> > Posted by Stoop, Hans On 11/19/2018 03:50 PM> > > > > > If you want to use roles that are similar to the roles that are used by projects and template workspaces then you run in similar issues. > Connected workspaces have more advanced mechanism to prevent possible issues. Most noteworthy is the group mapping mechanism where you can assign groups based on attribute values. In that case you don’t have to assign the users to the roles.> Group assignment support multiple attributes and multi-valued attributes. Also attribute changes are supported.> > > Both mechanisms can also be merged. Roles should only be used when they are really different for every workspace. For example when you have an employee workspace it makes sense to have a role for the employee to access its own workspace but the> HR employees should be given access based on the group mapping.> > > Hans> > On 19. Nov 2018, at 15:41, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:> > > > > eLink : Performance> > > > Performance> > > Posted by > uldis@contesto.no (Šilovs, Uldis) On 11/19/2018 09:39 AM > > > > > > > > > Thank you!> We're currently thinking about just using Connected Workspaces (decoupled from the leading APP). > How is the security checked for a normal user is when you enter a folder?> 1) 100 Connected Workspaces (each has 3 roles)> 2) 100 standard folders (each has 3 groups in the ACL)> > > > > > > > > > [To post a comment, use the normal reply function]> > > > Topic: > Performance> > > > Forum: > Content Server Development Forum> > > > Content Server: > My Support> > > > > > > > > > > > > [To post a comment, use the normal reply function]> > > ============================================================> > > Topic: Performance> https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=76086996&objAction=viewincontainer> > > Forum: Content Server Development Forum> https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=786303&objAction=view> > > Content Server:> https://knowledge.opentext.com/knowledge/cs.dll> > >

Greg Griffiths

It serves a purpose and adds value if used "correctly", if you have the right mix of users in groups for example then it works, if you have every user in every group then, like Folders, performance suffers a lot. The additional functionality does add value to many use cases. Just like anything, when used correctly its great, e.g. an ocean liner is great across the atlantic, but not ideal in a river.