PSA - Tip I found to help with Outlook slowness to load emails
I just wanted to share something I learned that helped me out a great deal with my Outlook desktop. I am running Outlook version 2512. I was having an issue where my Outlook was running frustratingly slow. Anything I tried to do in Outlook was sluggish, and especially opening, writing, and replying to emails was very painful. I would open an email and watch the ribbon load piece by piece across the top as it tried to load, and this could take 10 seconds or so for any email. Anything in Outlook was like this, as I tried to do anything and it was just load everything very slowly. For this PC, it's just a standard office PC with low specs to do the work. What I read, and observed through Task Manager, Outlook is using GPU to help with its processing. This basic office PC doesn't have a powerful GPU, so this was making it even slower. I found an article that suggested to disable hardware acceleration for Outlook. I did this and my Outlook has ran perfectly since, very quick and very snappy. This was a huge quality of life improvement. I created a registry key at: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Graphics DWORD(32-bit): DisableHardwareAcceleration 1 After this, a reboot is necessary. Just sharing this in case it helps someone else with the same issue.Lesson Learned #529: Troubleshooting Application Slowness Using SSMS Copilot
Some days ago, I worked on a support case where a customer reported application slowness affecting multiple users. Instead of jumping into traces or manually writing diagnostic queries, we used SSMS Copilot to investigate the issue. I would like to share with you how we diagnosed and understood the root cause. To illustrate the case, let’s walk through a simplified example: we create a new table, and right after that, we add a new column to it. CREATE TABLE Ejemplo2 (ID INT) BEGIN TRANSACTION ALTER TABLE dbo.eJEMPLO2 ADD NuevoCampo INT NULL Using SQL Server Management Studio and Copilot we executed the following prompt: Please, provide all currently running or suspended sessions. Include session ID, status, command, wait type (if any), application_name, wait time, and current SQL text. We got the following results: I executed multiple times the same prompt and always the session ID 67 is in suspended mode and Wait_type LCK_M_SCH_S, for this reason, I run a new prompt: Please, provide all sessions that are currently blocked by another session. Include session ID, the blocking session ID, wait type, and the blocked SQL text . At the end, I found that the session 51 is blocking the session ID 67 and for this reason, I run a new prompt: do we any have active transaction pending for commit for the session ID 51. So, I understand that the Session ID 51 has a transaction open, so, let's ask the details of the session 51, with a new prompt: Please, show the most recent SQL statement executed by session ID 51, even if the session is currently sleeping or not running any active request. Include the session status and login name as well. Use sys.dm_exec_connections and most_recent_sql_handle to retrieve the query text if necessary. Well, we identified the problem, the session ID 67 is running a SELECT * FROM sys.Ejemplo2 but it's beging blocked by the session 51. Session ID 51 hasn’t finished its transaction, and now we either need to commit, rollback, or kill that session, especially if we don’t have access to the application that owns it. Before resolving the issue, I asked Copilot an additional prompt: Please, explain why session ID 67 is currently waiting. Include the wait type, and explanation of that, the resource being waited on, how long it has been waiting (seconds), and the SQL text. Also identify if another session is blocking it. The name of the object and schema Please, provide recommendations to prevent or reduce this kind of blocking situation in the future, based on the current wait type and blocking scenario observed with session ID 67. Please, summarize all current blocking chains in the system. Include blocking session IDs, blocked session IDs, wait types, wait durations, login names, and SQL statements involved.General AVD Slowness
We have a pool of NV24s_V3 VMs running. The VMs have 170+ applications on them so we have to keep the total number of users per VM down to 12. That being said, I can power on one of our VMs, let it boot up and sit for 10-15 minutes to get through all its startup processes and then login. When I login and get to my desktop, OneDrive will sync for a bit, but outside of that the CPU is under 10%, RAM is under 10% used and Disk Util is 15-20%. Even with those numbers low and me being the ONLY user on the VM, its still slow to open applications. It even takes 5-6 seconds for File Explorer to open. I see defender processes running under Disk stats, but it alone shouldnt be causing that kind of slow down, especially when the CPU / RAM / Disk stats are low. Anyone have any advice of something to look at to speed up performance? We have already excluded Defender from scanning Program Files and Program Files (x86). Just very troubling that its slow with just 1 user logging onto a 24 proc, 200+ GB RAM VM.
