Replies: 1 comment 2 replies
-
Superset interprets angle brackets ( Performance degradation after enabling HTML rendering is likely due to increased DOM complexity and React rendering overhead. Rendering raw HTML in many table cells forces the frontend to do extra parsing, escaping, and potentially unsafe rendering, which slows down UI updates—especially with large datasets. The DataTable component uses React hooks and memoization for optimization, but rendering HTML content in cells can bypass these optimizations and increase computation per cell, leading to slower table rendering [source]. If you want to display angle brackets as plain text and improve performance, it's best to keep HTML rendering disabled for your tables. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I found two related issues in Superset when working with MySQL data:
1.Field values with angle brackets are missing
In MySQL the value is:

(HOFO,6hd, 6.0)
But in Superset it only shows:
(HOFO,6hd, 6.0)
This happens at row 144 — the and parts are missing there. The problem is inconsistent: some <...> fragments are preserved, others are hidden.
The text inside < > is missing (not all brackets are dropped, but some).
I have already enabled RENDER COLUMNS IN HTML FORMAT, but the issue still happens.
Expected: Superset should display the text exactly as stored in MySQL, including < >.
2.Performance issue after enabling HTML rendering
Previously, Superset did not have the RENDER COLUMNS IN HTML FORMAT option.
Our DevOps team added this feature by editing .tsx files and rebuilding the image.
After rebuilding, Superset became noticeably slower when rendering tables.
Why would enabling this option and rebuilding cause such performance degradation?
Beta Was this translation helpful? Give feedback.
All reactions