Hello! I'm experiencing some serious performance issues while using mutagen. Here's the output of

top

inside the container:

Load average: 22.94 23.11 20.13 17/1455 351
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
  275     0 root     S     965m   8%   1  12% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  258     0 root     S     966m   8%   4  12% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  224     0 root     S     965m   8%   1  11% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  240     0 root     S     966m   8%   3  11% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  204     0 root     S     966m   8%   2  11% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  293     0 root     S     966m   8%   0  10% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  165     0 root     S     966m   8%   2  10% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
  188     0 root     S     965m   8%   5  10% .mutagen/agents/0.12.0-beta2/mutagen-agent synchronizer
    1     0 root     S     686m   6%   2   0% /usr/bin/mutagen-sidecar-entry
  344     0 root     S     1648   0%   4   0% sh
  351   344 root     R     1580   0%   4   0% top

Is there any way to solve it? My laptop is barely usable when spryker is up.

Are you using mac OS or Linux? Linux helped me

I'm using macOS

Hi, have you tried to terminate your mutagen syncing sessions? You can try executing

mutagen list

to see the sync sessions list, and then try terminating each of them via

mutagen sync terminate <session_name>

. Maybe that would help you

@great-afternoon-41358 Thank you, it was exactly the case. For some reason, I had 12 sessions run at the time, so I killed 11 of them and it worked like a magic.

That’s nice to hear 😉

Indeed, I found the issue

Make sure you have latest mutagen version

I'm using 0.12.0-beta2, which is the latest one in beta channel. Or should I switch to dev one?

I have the restart my mac after a few hours of developing because the mutagen process uses 2 GB or more and becomes unreliable.

Class XXTransfer not found

and other random issues.

How many mutagen sessions do you have there?

currently 3 (1 paused) but sometimes just one

It should be only one for one project.

I just booted my machine but it still had 2 or 3 "old" sessions

And I wonder why is it so. For me it does not recreate extra sessions. Would it be related to docker version…

docker version
Client: Docker Engine - Community
 Cloud integration: 1.0.9
 Version:           20.10.5
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        55c4c88
 Built:             Tue Mar  2 20:13:00 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.5
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       363e9a8
  Built:            Tue Mar  2 20:15:47 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

mutagen version 0.12.0-beta2

I have a feeling that it could be related specifically to

run

command. What if use only

up

one?

just FYI: I never use

run

it would be helpful if we see the reproducible steps of the issue, what causes the duplication. Would you try, please, to catch the exact flow that brings the problem.

@high-pencil-62400 it seems like using

Restart

on

Docker Desktop

will create an additional sync session

Awesome! Thank you for finding the root cause. That will help much!

I think so it is normal that happened it... Because by following UP the sdk just create another mutagen session and the previoulsy is still there.. Each time that i restart Docker at first stop the

docker/sdk down

and then restart docker and finally again

docker/sdk up

It should not happen this way. Mutagen should catch that and reuse the session. I will create a ticket for that. However we can add a check of other existing session to terminate them.

yes, I run docker/sdk up