Hi,
We recently conducted a production upgrade, and as a result, the end application has become significantly slower. We've observed that the following procedure is being invoked for each user. It appears that this procedure is called during startup, leading to a prolonged delay. How can we address and resolve this issue?
/* Create or alter stored procedure get_gui_elemnt. */
- session_id 151, cpu_time: 212742, total_elapsed_time: 750783
- session_id 153, cpu_time: 251607, total_elapsed_time: 1344832
- session_id 160, cpu_time: 240716, total_elapsed_time: 1293270
- session_id 178, cpu_time: 250101, total_elapsed_time: 623093
- session_id 231, cpu_time: 133600, total_elapsed_time: 436721
GUI version: 2023.1.10.0.1
Windows GUI and Universal are slow.
My second question is: Can someone explain to me the origin of this query and why it is consistently running or suspended?
(@source nvarchar(256))SELECT type, data FROM sys.fn_MSxe_read_event_stream (@source, 0)
session info:
- host_name: DB4C000001
- program_name: TdService
- nt_domain: NT AUTHORITY
- login_name: NT AUTHORITY\SYSTEM
- status: suspended
- cpu_time: 12
- total_elapsed_time: 1760436
The query in question is causing performance concerns, and I would appreciate insights into its source and the reasons for its persistent execution or suspension.
Best answer by Gosia
View original
