Assigning New Grants to User Takes Long Time.

[vogtjob]

Is there an existing issue for this?

• I have searched the existing issues

Are you using the latest version of STIG Manager?

• I am using the latest Release.
• I am NOT using the latest Release. I am aware that the first thing I will be asked to do is update the application so that I have the latest bugfixes.

Where are you experiencing the issue?

• API
• UI or other client
• Deployment
• Elsewhere

Current Behavior

When modifying a user through Application Management->User Grants it takes a long time for the collection drop-down to populate (3-4 minutes). During this period of lag time the mysql CPU usage is 100% until the query being performed completes. The instance this occurs on is quite large (rows from application info): 98 collections, 43,969 assets, 22,238,926 review, 26,703,470 review history.

Expected Behavior

Collection drop-down populates from Application Management->User Grants populates quicker.

Steps To Reproduce

No response

Can you provide screenshots, logs, or other useful artifacts?

No response

Describe your Environment

- Hosting:
- Browser: Chrome, Edge
- OS: RHEL 8.10 (podman containers)
- Node:
- npm:

[cd-rite]

Hi @vogtjob Wow, I'm surprised you waited that long before giving up!
I can see some performance issues with the endpoint (getCollections) in play here, but our testing did not reveal an impact as large as yours.

We have a feature branch implementing User Access Controls that we are targeting for October that we expect should resolve this issue, but we will look into addressing this separately and before that release if feasible.

Can you provide the Anonymized Deployment Details report available from the app? This will help us model your circumstances to ensure we can recreate and address the issue accurately. It will also help us determine if you may see better performance with a database setting change before any fix we may make.

What is your performance like when loading the App Management->Collections UI? That UI hits the same endpoint as the Modify User interface, but with slightly different parameters.
If that interface loads more quickly, it may be more tolerable to assign Grants via the App Management->Collections UI instead of the User Management UI for now. You'll be adding Users to Collections, rather than adding Collections to Users.

[vogtjob]

Hi, The Collections UI does load a lot quicker (30 seconds maybe) and this works better if a user is only needed to be added to one/few collections. But some need access to most/all which is when we'll go the other method and wait it out. I will try to get the Anonymized Deployment report to this network, but that is a process that could take some time. If there are specific items of interest, I could translate them here. If there are changes coming in October that will resolve this, that is excellent news! Thanks you.

…

On Thu, Sep 19, 2024 at 6:20 PM cd-rite ***@***.***> wrote: Hi @vogtjob <https://github.com/vogtjob> Wow, I'm surprised you waited that long before giving up! I can see some performance issues with the endpoint (getCollections) in play here, but our testing did not reveal an impact as large as yours. We have a feature branch implementing User Access Controls that we are targeting for October that we expect should resolve this issue, but we will look into addressing this separately and before that release if feasible. Can you provide the Anonymized Deployment Details report available from the app? This will help us model your circumstances to ensure we can recreate and address the issue accurately. It will also help us determine if you may see better performance with a database setting change before any fix we may make. What is your performance like when loading the App Management->Collections UI? That UI hits the same endpoint as the Modify User interface, but with slightly different parameters. If that interface loads more quickly, it may be more tolerable to assign Grants via the App Management->Collections UI instead of the User Management UI for now. You'll be adding Users to Collections, rather than adding Collections to Users. — Reply to this email directly, view it on GitHub <#1376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4P6FRWXTBHABIO5ARW6QO3ZXNEZZAVCNFSM6AAAAABOPYEVSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSGMYDAMZUHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[cd-rite]

Should be resolved when #1289 is resolved.