Re:Reducing Slack’s memory footprint
by coldtea on Saturday March 04, 2017 @05:58AM
(#13790338)
"...with a single team of 5 and 2 channels".
Seriously, it's not about "running just fine", it's about how many resources it uses. Even the startup time is awful for what it does.
And the Slack team itself recognizes that there are issues -- as seen in TFA:
"However, these capabilities come at a cost: the desktop client can use a lot of memory. This memory footprint increases as the user signs into more teams, as each team runs in its own webview. More memory usage means worse performance, degrading our customer’s experience of Slack and their other applications."
and:
"At the time of writing, about 36% of active Slack users are signed into more than one team in the desktop app. 17% are signed into 3 or more teams, and 5% are signed into 5 or more teams. Each of these teams is running the full JavaScript web application and maintaining and updating the DOM tree as the state of the team changes. This application can consume between ~130MB (p10) and ~960MB (p99) of memory depending on team activity and UI state."
Seriously, it's not about "running just fine", it's about how many resources it uses. Even the startup time is awful for what it does.
And the Slack team itself recognizes that there are issues -- as seen in TFA:
"However, these capabilities come at a cost: the desktop client can use a lot of memory. This memory footprint increases as the user signs into more teams, as each team runs in its own webview. More memory usage means worse performance, degrading our customer’s experience of Slack and their other applications."
and:
"At the time of writing, about 36% of active Slack users are signed into more than one team in the desktop app. 17% are signed into 3 or more teams, and 5% are signed into 5 or more teams. Each of these teams is running the full JavaScript web application and maintaining and updating the DOM tree as the state of the team changes. This application can consume between ~130MB (p10) and ~960MB (p99) of memory depending on team activity and UI state."