Daily Learning Log Entry Date: July 10, 2025 Developer: Abdul Rahman Kidwai Project: Group Deletion Performance Optimization 🎯 Problem Statement Group deletion operations were taking 10+ minutes for 376 filter deletions, causing poor user experience and potential timeout issues. 🔍 Learning & Discovery Process Initial Investigation Assumption : Blob storage was the bottleneck Reality Check : Database operations were the real performance killer (80-200 seconds per operation) Key Insight : Always profile before optimizing - assumptions can be wrong Root Cause Analysis Database Issues : 376 individual SQL operations instead of bulk operations Azure Storage Throttling : Unlimited concurrent requests triggering rate limits Thread Pool Concerns : Risk of exhausting web server resources with long-running operations 🔧 Technical Solutions Implemented 1. Database Bulk Operations (Primary Solution) Before : 376 individual DELETE statements After : 3 bulk SQ...
Chart.JS does works if parent is hidden(), did't know this! Get-WmiObject -Class Win32_Process -Filter "Name='w3wp.exe'" | Select-Object ProcessId, CommandLine Key Insights You Learned: 1. CPU and RAM are connected, but different problems High CPU usage can be a symptom of insufficient RAM When RAM runs low, the system uses slow disk storage, making CPU work harder managing the traffic 2. Diagnostic data tells a story 75% RAM usage + 100 hard faults/sec + high disk I/O = classic memory pressure Task Manager shows what's happening , IIS Manager shows which app is responsible 3. Memory has multiple dimensions Private Bytes = actual RAM your app is using (841 MB) Virtual Bytes = total memory space reserved (2.17 GB - the bigger concern!) 4. Context matters for memory usage judgment 841 MB could be normal or a leak - depends on what the application actually does Simple CRUD app using 841 MB? Suspicious. File processing app? Possibly normal. 5. Both...
# Requires Microsoft.Graph module: Install-Module Microsoft.Graph -Scope CurrentUser # --- Configuration --- # <<<<< IMPORTANT: REPLACE WITH YOUR TEST TENANT ID >>>>> $tenantId = "515FF807-4698-4D87-8380-98D33D7BE5XX" $baseGroupDisplayNamePrefix = "HyperAggroTestGroup" # This matches the prefix used in the aggressive scripts Write-Host "Starting cleanup: Deleting all groups with DisplayName starting with '$baseGroupDisplayNamePrefix' in Tenant: $tenantId" Write-Host "-----------------------------------------------------------------------------------------------------" # --- Connect to Microsoft Graph --- # Ensure you are connected with the necessary permissions (Group.ReadWrite.All) try { # Removed -Force parameter from Connect-Mggraph Connect-Mggraph -Scopes "Group.ReadWrite.All" -TenantId $tenantId Write-Host "Successfully connected to Microsoft Graph." } catch { Write...
Comments
Post a Comment