Open Ramudaykumar opened 1 year ago
Hi @Ramudaykumar
I've captured from v1.44.1: Consistent 100% usage for this scenario, and I think that's just a lot of content being rendered at once that's causing this!
leading to doubled Dom components when opened recommendation second time:
So you can see that components are not clearing out and are leaking resources.
What's different in ADS now is that it's crashing instead - that was still taking up that load before. @aasimkhan30 anything we can do here to allow this massive Dom component usage?
Here's a script to create (and drop) 500 dbs for testing if anyone else is looking at this
-- CREATE
declare @i int = 1
while @i < 500
begin
declare @script nvarchar(max) = 'CREATE DATABASE testdb' + CAST(@i as nvarchar)
exec sp_executesql @script
set @i = @i + 1
end
-- CLEANUP
/**
DECLARE @cmd nvarchar(max)
DECLARE cmds CURSOR FOR
SELECT 'drop database [' + name + ']'
FROM sys.databases
WHERE name LIKE 'testdb%'
OPEN cmds
WHILE 1 = 1
BEGIN
FETCH cmds INTO @cmd
IF @@fetch_status != 0 BREAK
EXEC(@cmd)
END
CLOSE cmds;
DEALLOCATE cmds
*/
Ran SKU recommendation again on a fresh instance of ADS 1.45-RC1.. I see it loaded report properly.. and held up to resources/DOM nodes:
Report generated successfully for 604 databases:
So it seems Crashes are not consistently happening too, it only crashed once for me but I could restart ADS and continue again. App hangs same way as it does in 1.44.1 and CPU usage is also consistent.
Hi @Ramudaykumar
Is this issue still occurring with latest insiders build?
Steps to Reproduce:
Flickering recording Profiling of ADS
Does this issue occur when all extensions are disabled?: No (I cannot find any tree view without extension so can't reproduce without