ssb-patchwork process grew to 50% of memory use in top, on my 4 gb ram laptop. Luckily, restarting it dropped memory to 2%.
That process started life with a mostly empty ~/.ssb and downloaded all the backlog. Then I went offline for several hours and browsed pretty extensively through old posts, including scrolling many months back. So the memory use was probably caused by one of those things.
joeyh
All 9 comments
(Using patchwork-3.2.2-linux-x86_64.AppImage)
joeyh
on 7 Apr 2017
Hey, thanks for opening this issue. Are you still having this issue on the latest Patchwork? I think #858 may be relevant as well.
christianbundy
on 7 Nov 2018
I have not noticed patchwork eating quite that much memory lately.
--
see shy jo
joeyh
on 7 Nov 2018
Isn't that the habit of electron applications in general?
Serkan-devel
on 8 Nov 2018
@Serkan-devel it's the habit of web applications in general, as most web developers don't think to care about memory performance, electron is just an easy way to make a web application into a desktop application. fortunately Matt (who i consider _the_ expert in JavaScript memory performance from his work on Loop Drop) has invested a heap of time and energy into reducing bloat: https://github.com/mmckegg/patchtron, https://github.com/ssbc/patchwork/issues/858.
ahdinosaur
on 8 Nov 2018
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
![stale[bot] picture](https://avatars.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 23 Apr 2019
Or could one just rewrite patchwork/ssb into something that isn't javascript?
It might reduce memory usage even further when it's written in something like Crystal
Serkan-devel
on 19 May 2019
@Serkan-devel: i agree with what you're saying (see the Sunrise Choir for a complete re-write in Rust), but i don't appreciate how you're saying this ("one could just..." :confused: ) . if you want to reduce memory usage in Scuttlebutt, please help us by contributing!
to paraphrase %4JT/+ITi0ecWU8n1/DWqt3+SNxagF76b33MyJ/CAdTU=.sha256:
I mean I believe [we need] people working on hard problems… more than [we need] people confirming that [hard problems exist]
ahdinosaur
on 20 May 2019
I have not noticed patchwork eating quite that much memory lately.
Closing (not that performance is ever a solved problem).
Powersource
on 9 Jun 2019
Related issues
cinnamon-bun
·
4Comments
mmckegg
·
5Comments
Logicbloke
·
7Comments
skippednote
·
6Comments
molstrangler
·
7Comments
Most helpful comment
@Serkan-devel it's the habit of web applications in general, as most web developers don't think to care about memory performance, electron is just an easy way to make a web application into a desktop application. fortunately Matt (who i consider _the_ expert in JavaScript memory performance from his work on Loop Drop) has invested a heap of time and energy into reducing bloat: https://github.com/mmckegg/patchtron, https://github.com/ssbc/patchwork/issues/858.