Rendering large tables is very slow

%3CLINGO-SUB%20id%3D%22lingo-sub-1460579%22%20slang%3D%22en-US%22%3ERendering%20large%20tables%20is%20very%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1460579%22%20slang%3D%22en-US%22%3E%3CP%3ERendering%20of%20large%20tables%20is%20very%20slow%20on%20Chromium%20browsers%20compared%20to%20others.%3C%2FP%3E%3CP%3EAttached%20is%20an%20example%20of%20a%20(legacy)%20table%20containing%20roughly%202250%20rows%20and%2031000%20cells.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERendering%20times%20on%20my%20machine%3A%3C%2FP%3E%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%3CTBODY%3E%3CTR%3E%3CTD%20width%3D%2250%25%22%3E%3CSTRONG%3EBrowser%3C%2FSTRONG%3E%3C%2FTD%3E%3CTD%20width%3D%2250%25%22%3E%3CSTRONG%3ERendering%20time%3C%2FSTRONG%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2250%25%22%3EEdge%2083.0%20x64%3C%2FTD%3E%3CTD%20width%3D%2250%25%22%3E15.4s%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2250%25%22%3EChrome%2083.0%20x64%3C%2FTD%3E%3CTD%20width%3D%2250%25%22%3E15.2s%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2250%25%22%3EMSEdge%2044.18362%3C%2FTD%3E%3CTD%20width%3D%2250%25%22%3E2.0s%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2250%25%22%3EIE%2011%3C%2FTD%3E%3CTD%20width%3D%2250%25%22%3E1.5s%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2250%25%22%3EFF%2077.0.1%20x64%3C%2FTD%3E%3CTD%20width%3D%2250%25%22%3E1.3s%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20known%20issue%20in%20Chromium%20since%20at%20least%202015%20(%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D461877%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D461877%3C%2FA%3E)%20but%20apparently%20they%20have%20no%20intent%20of%20solving%20the%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20issue%20known%20for%20the%20new%20Edge%20browser%20and%20are%20there%20any%20plans%20of%20fixing%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1460938%22%20slang%3D%22en-US%22%3ERe%3A%20Rendering%20large%20tables%20is%20very%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1460938%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F698364%22%20target%3D%22_blank%22%3E%40Erich11%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F470968%22%20target%3D%22_blank%22%3E%40MissyQ%3C%2FA%3E%26nbsp%3BI%20tried%20it%20and%20the%20table%20loading%20speed%20is%20insanely%20slow%2C%20especially%20compared%20to%20other%20browsers%20which%20do%20it%20instantly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1462593%22%20slang%3D%22en-US%22%3ERe%3A%20Rendering%20large%20tables%20is%20very%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1462593%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343543%22%20target%3D%22_blank%22%3E%40cjc2112%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F698364%22%20target%3D%22_blank%22%3E%40Erich11%3C%2FA%3E%26nbsp%3BIts%20blazingly%20fast%20in%20edge%20legacy.%20Comparing%20edge%20legacy%20with%20current%20chromium%20edge%20browser%2C%20edge%20legacy%20tops%20both%20in%20terms%20of%20performance%2C%20and%20features.%20The%20current%20chromium%20edge%20browser%20should%20have%20atleast%20have%20as%20many%20features%20as%20in%20edge%20legacy.%20Why%20the%20edge%20legacy%20disowned%20is%20because%20it%20uses%20a%20different%20rendering%20style%20of%20web%20controls.%20But%20in%20terms%20of%20performance%20its%20still%20the%20best%20browser.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1464225%22%20slang%3D%22en-US%22%3ERe%3A%20Rendering%20large%20tables%20is%20very%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1464225%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F698364%22%20target%3D%22_blank%22%3E%40Erich11%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343543%22%20target%3D%22_blank%22%3E%40cjc2112%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F620509%22%20target%3D%22_blank%22%3E%40sauravyad500%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20all%20for%20bringing%20this%20to%20our%20attention.%20I'll%20ask%20our%20team%20to%20look%20into%20this%20and%20see%20if%20there's%20anything%20we%20can%20do%20on%20our%20side%20of%20this.%20If%20you%20haven't%20yet%2C%20can%20you%20please%20submit%20diagnostics%20through%20the%20browser%20for%20this%3F%20(Shift%2BAlt%2BI)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3E%3CBR%20%2F%3EProject%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1464340%22%20slang%3D%22en-US%22%3ERe%3A%20Rendering%20large%20tables%20is%20very%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1464340%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20passing%20this%20on%20to%20your%20team.%20I've%20already%20submitted%20diagnostics%20last%20week%2C%20I%20just%20don't%20know%20if%20this%20will%20help%20you%20as%20the%20website%20is%20internal%20only%20(our%20age%20old%20ERP%20system).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20finally%20moved%20from%20IE11%20to%20Edge%20last%20month%20and%20I%20thought%20that%20I%20have%20tested%20everything%20thoroughly.%20Seems%20like%20I%20didn't.%20For%20now%20it%20is%20not%20a%20big%20deal%20as%20there%20aren't%20that%20many%20views%20with%20huge%20tables%2C%20but%20everyone%20who%20stumbles%20across%20them%20is%20complaining%20about%20the%20loading%20times.%3C%2FP%3E%3CP%3EI%20will%20now%20try%20to%20rewrite%20our%20table%20generator%20with%20grid-layout%2C%20proof%20of%20concept%20is%20looking%20very%20promising%20(rendering%20times%20down%20to%20about%20200ms).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENevertheless%20it%20would%20be%20amazing%20to%20see%20a%20fix%20for%20this%20anytime%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20thanks%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343543%22%20target%3D%22_blank%22%3E%40cjc2112%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F620509%22%20target%3D%22_blank%22%3E%40sauravyad500%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bfor%20confirming%20my%20test%20results%20%3A).%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1463705%22%20slang%3D%22en-US%22%3ERe%3A%20Rendering%20large%20tables%20is%20very%20slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1463705%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F620509%22%20target%3D%22_blank%22%3E%40sauravyad500%3C%2FA%3E%26nbsp%3BIts%20also%20%22blazing%20fast%22%20on%20every%20other%20browser%20except%20chromium%20based.%20I%20confirmed%20his%20results%20on%20my%20own%2C%20even%20explorer%20takes%201%20second.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Rendering of large tables is very slow on Chromium browsers compared to others.

Attached is an example of a (legacy) table containing roughly 2250 rows and 31000 cells.

 

Rendering times on my machine:

BrowserRendering time
Edge 83.0 x6415.4s
Chrome 83.0 x6415.2s
MSEdge 44.183622.0s
IE 111.5s
FF 77.0.1 x641.3s

 

This is a known issue in Chromium since at least 2015 (https://bugs.chromium.org/p/chromium/issues/detail?id=461877) but apparently they have no intent of solving the problem.

 

Is this issue known for the new Edge browser and are there any plans of fixing it?

5 Replies
Highlighted

@Erich11 @MissyQ I tried it and the table loading speed is insanely slow, especially compared to other browsers which do it instantly. 

Highlighted

@cjc2112 @Erich11 Its blazingly fast in edge legacy. Comparing edge legacy with current chromium edge browser, edge legacy tops both in terms of performance, and features. The current chromium edge browser should have atleast have as many features as in edge legacy. Why the edge legacy disowned is because it uses a different rendering style of web controls. But in terms of performance its still the best browser.

Highlighted

@sauravyad500 Its also "blazing fast" on every other browser except chromium based. I confirmed his results on my own, even explorer takes 1 second.

Highlighted

@Erich11 @cjc2112 @sauravyad500 

 

Thank you all for bringing this to our attention. I'll ask our team to look into this and see if there's anything we can do on our side of this. If you haven't yet, can you please submit diagnostics through the browser for this? (Shift+Alt+I)

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

Highlighted

@fawkes 

Thank you for passing this on to your team. I've already submitted diagnostics last week, I just don't know if this will help you as the website is internal only (our age old ERP system).

 

We finally moved from IE11 to Edge last month and I thought that I have tested everything thoroughly. Seems like I didn't. For now it is not a big deal as there aren't that many views with huge tables, but everyone who stumbles across them is complaining about the loading times.

I will now try to rewrite our table generator with grid-layout, proof of concept is looking very promising (rendering times down to about 200ms).

 

Nevertheless it would be amazing to see a fix for this anytime soon.

 

Also thanks to @cjc2112 @sauravyad500 for confirming my test results :).