Open evilaliv3 opened 10 years ago
Doing a little bit of research I found this:
http://blog.scalyr.com/2013/10/31/angularjs-1200ms-to-35ms/ - They seem to be using an approach similar to what you descibed in ticket #774, by inhibiting the watchers by means of a special directive.
Applying label Performance. Has this been fixed?
a GLClient performance profiling need to be addressed
it's seems that some part of AngularJs are taking so much CPU and so probably needs refactoring.
in particular some pages are critical when so much populated:
this is needed in reference of https://github.com/globaleaks/GlobaLeaks/issues/774
/cc @vecna @fpietrosanti
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.