How to troubleshoot when end users complain that the data steward application is very slow - including taking more than 10 seconds to open a Business View (BV), taking more than 1 minute to check out records in a duplicate management workflow, etc.

...

1. Turn on logging for the data steward application. Follow these instructions.
2. Gather benchmarks metrics to track what is slow. Time however long it takes to perform the task that the customer complains is sluggish.
3. For example, pick a BV. Open the golden data view only. See error log for how long that task took and retrieve the SQL that ran.
4. Run the SQL in SQL Developer. Does it take the same amount of time to execute as it does in Semarchy? 
5. Get the an explain plan.  

...

Top culprit for slow performance in a Collection: Sorting

Sort is a highly suspicious component that might be causing bad performance. Sorting requires ordering and the order by is a very expensive task that can cause the application to slow down significantly. The use of an index can have an enormous beneficial impact.

Oracle example: Look at the "Sort order by stopkey" cost. Does it seem like a higher cost than the other tasks (like joins) in the explain plan? 
PostgreSQL and MS SQL Server have different syntax, but the same concept applies.

To test, comment out remove the order by statement. Execution now takes much less than 10 seconds? Probably You are probably experiencing an issue with sorting.

Top culprit for slow performance in a Form: Embedded Collections

Embedded collections require many queries.

Step 2: Troubleshooting in Semarchy

1. Open the BV in the workbench. Under "Collection Configuration", look at Customized Sort. Are there any attributes sorted? If yes, remove all attributes. This should increase speed of application because the BV will now rely on default sorting based on the ID. This will normally be faster because it is indexed.
   Alternative: It's possible to manually add an index in the database schema. If your users have an important business need for the Customized Sort, then keep the sort. And add an index to provide good performance for this sort.
2. Open the BV in the workbench. Under "Collection Configuration", look at "User-Defined Sort". Is user-defined sorting allowed? If so, it's possible for users to set sorts that may perform poorly. 
   Option 1: disallow user-defined sorts.
   Option 2: educate users that default sorting is fast, but user-defined sorting may be slow. Use it only on filtered data.
3. If there's still bad performance or even a Null Pointer Exception (NPE) when opening BVs, sort preferences might have been corrupted. Go to User Profile → Settings. Use the 'clear' option to remove "Selected columns, sort order and type of view used" Getting rid of these saved preferences usually solves the problem.
4. (Legacy 3.x reference) Under Preferences → Data Stewardship, uncheck Predictable Pagination. 

Dupes Mgmt Workflow takes a long time 

Step 1: Troubleshooting in Semarchy

...