Patchwork is pretty CPU intensive while idling about patchwork HOT 19 CLOSED

Oh wow, that's brutal. I'm seeing the same thing. Going to diagnose.

from patchwork.

does scuttlebot have the same thing? if so can you disable plugins until it goes away?

from patchwork.

thats what I'm going to try, starting with the gossip plugin

from patchwork.

It's the animated gifs and webms. In ./ui/lib/markdown.js#renderer.image you can disable the embeds and resolve the issue completely.

The animated gifs are separate from webms, and they are just as intensive. (I'm able to test this thanks to david's p2p gif.)

from patchwork.

Yeah, it's the animation. Pausing the videos and hiding the gifs solves it. (Thankfully, setting visibility to hidden fixes the gifs, so the layout wont have to reflow.)

I'll have to watch element visibility and enable/disable as you scroll (darn!)

from patchwork.

fixed in f929c75

from patchwork.

I'm still seeing this:

on my linux vps:

on my 8 core mac:

from patchwork.

@gardner what version are you on? I'm trying to figure out what causes this. but am having trouble reproducing.

from patchwork.

@gardner this is an old thread, that correctly diagnosed a different CPU over-use bug in the Patchwork frontend. We're working on what you're experiencing now

from patchwork.

scuttlebot@drinkbot:~$ sbot version
7.5.2

Should I open a new issue for this? I don't seem to get anything useful when I run it under the profiler...

note @kOK REPL @uRECWB4KIeKoNMis2UYWyB2aQPvWmS3OePQvBj2zClg=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @hGd3sjghbrkVaFEMUrXV11m2oyKLfLqJQcadvapH02w=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @hGd3sjghbrkVaFEMUrXV11m2oyKLfLqJQcadvapH02w=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @0GLMsG6IgXdv+GjG0U5UnZlwxHnomlfmrlWugx8i4dg=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @hxGxqPrplLjRG2vtjQL87abX4QKqeLgCwQpS730nNwE=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @/02iw6SFEPIHl8nMkYSwcCgRWxiG6VP547Wcp1NW8Bo=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @uRECWB4KIeKoNMis2UYWyB2aQPvWmS3OePQvBj2zClg=.ed25519 success
  "Feeds updated: 1, New messages: 1"
note @kOK REPL @uRECWB4KIeKoNMis2UYWyB2aQPvWmS3OePQvBj2zClg=.ed25519 success
  "Feeds updated: 1, New messages: 1"
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync
Device sleep detected, triggering pub sync

from patchwork.

BTW this is running on a VPS and was installed via npm install.

uname -a
Linux drinkbot 2.6.32-042stab113.11 #1 SMP Fri Dec 18 17:32:04 MSK 2015 x86_64 x86_64 x86_64 GNU/Linux

from patchwork.

Let's say ssbc/ssb-server#270 is our canonical thread for backend CPU usage issues

from patchwork.

@gardner we had a bug in the quota system.. we are still deciding what to do about this, but for now if you run sbot in "party" mode, it will disable that, and shouldn't have this problem. ssb_party=1 sbot server will do it.

from patchwork.

or set "party": true in ~/.ssb/config

from patchwork.

I'm not sure if the party is happening. Is the .ssb/config file a json file?

scuttlebot@stormcloud:~$ cat .ssb/config 
"party": true
scuttlebot@stormcloud:~$ 

from patchwork.

@gardner config is a JSON file, it should be

{"party": true}

from patchwork.

note, you need to be running at least [email protected] for this party mode to work.

from patchwork.

Thanks guys! {"party": true} in my config file has fixed the cpu utilization problem that I was having. This process has been running for 2 days and only utilized 3.5 hours cpu:

from patchwork.

That's good to hear, thanks for the update

from patchwork.