[BUG] CPU activity when the app is paused syncing

[vlad-cotfas]

Catalina 10.15.4
Maestral 1.0.2

cpuActivity.mov.zip

See the attached files, I see it is still doing CPU activity when the Maestral app is paused syncing.

[vlad-cotfas]

Also when the app is still in pause, it has energy impact on the battery..

I normally put the Maestral app on pause when I`m on battery or I need the full bandwidth of the internet and CPU/RAM resources for intensive work.

[samschott]

Yes, I am aware of the issue and already have a fix for the next release...

[samschott]

It's the GUI and not the daemon process which is causing the high CPU usage. Therefore, you can mitigate this by running the daemon without the GUI through the command line interface for now.

It's not as convenient, unfortunately, but you can start a GUI as necessary and it will attach itself to the running daemon. You'll notice that the "Quit Maestral" menu entry changes to "Quit Maestral GUI" which indicates that quitting the GUI will leave the daemon running.

[vlad-cotfas]

Yes, but I kinda need the statusbar to know what is going on.. :(

[vlad-cotfas]

If I`m switching to the terminal version from the GUI, I can switch it back with cli:

maestral gui

And to pause/start:

maestral pause|resume

And to see what has been synced:

maestral status

Do I have to do the:

maestral autostart

To register it with Mac startup?

Right?

[samschott]

Yes! Although maestral autostart only registers the daemon to start on login and not the GUI.

I'll see if I can get a beta release out with bug fixes soon.

[vlad-cotfas]

From the GUI I have disabled the autostartup, and from the CLI when I do:

maestral autostart

I get:

Autostart is disabled.

I did not restarted my mac yet to see if is ok.

[vlad-cotfas]

It does not restart the daemon on mac restart.

cotfas:~ work$ maestral status
Maestral daemon is not running.

And after restart, I got again the GUI maestral dialog error from #137

[samschott]

The GUI command to enable autostart is:

maestral autostart -Y

maestral autostart only returns the current status. Yeah, I am working on #137 but its difficult to debug...

[vlad-cotfas]

cotfas:~ work$ maestral autostart -Y
Enabled start on login.
cotfas:~ work$ maestral autostart
Autostart is enabled.
cotfas:~ work$

Perfect :)

Maybe update the repo readme file to be updated with the commands for mac as well, I did not knew about -Y param.

And the help guide does not give to much info:

cotfas:~ work$ maestral -h
usage: main [-h] [-c CONFIG_NAME] [--cli] [--frozen-daemon]

optional arguments:
-h, --help show this help message and exit
-c CONFIG_NAME, --config-name CONFIG_NAME
Configuration name
--cli Forward calls to CLI.
--frozen-daemon Start daemon only
cotfas:~ work$

[vlad-cotfas]

Will let you know on next reboot if the maestral autostart -Y worked. Thanks.

[vlad-cotfas]

Wow, definitely will use the daemon/cli instead of GUI from now on as I see the memory/cpu/energy impact looks way better.

@samschott good job, keep up the good work, don`t forget about #144 please. :)

[samschott]

There is a beta out now which reduces the CPU usage of the GUI to more reasonable levels.

Wow, definitely will use the daemon/cli instead of GUI from now on as I see the memory/cpu/energy impact looks way better.

Yes, the cocoa UI uses about as much memory as the daemon itself...