We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
如题,做了个对比试验,57列 * 500行,使用Regular做纯粹的渲染工作都要消耗290m内存,对比了纯静态的html页面,相同的结构只占用148m内存,很崩溃,实际业务远比这个demo要复杂,内存压力很大。 demo: https://codepen.io/kaola-fed/pen/OELNqo
The text was updated successfully, but these errors were encountered:
简单排查问题应该出现在#inc ,临时解决能否将模板先写死 <td>{{item.categoryName}}</td>这个结构呢?
#inc
<td>{{item.categoryName}}</td>
Sorry, something went wrong.
谢谢提醒!但是这个列表的字段数量非常多,并且很多字段都有自己的交互逻辑,并不是纯展现,大致可以分成10种以上的处理方式,并且每个字段可能会根据业务计算出不同的形态,字段的处理逻辑最初是直接写在列表的模板里面的,发现模板里面加人太多逻辑之后,情况很糟糕,就换成用js提前处理好再传进去,效果好很多。 然后,这个问题我应该属于长列表的问题,我准备从侧面去解决,只显示用户可见的数据。
应该是inc的 实现问题。 去掉后, 发现和Vue的内存占用保持一致。 React 比较麻烦些,就没有做对比。
我找时间做个优化,这个问题没有最终解决, 我先reopen把
谢谢!辛苦大佬!
No branches or pull requests
如题,做了个对比试验,57列 * 500行,使用Regular做纯粹的渲染工作都要消耗290m内存,对比了纯静态的html页面,相同的结构只占用148m内存,很崩溃,实际业务远比这个demo要复杂,内存压力很大。
demo: https://codepen.io/kaola-fed/pen/OELNqo
The text was updated successfully, but these errors were encountered: