S3Drive - New 1.13.0 mac os performance issue

After I updated to 1.13.0 on my M4 macbook air, I find it is constantly using around 15-20% of CPU in background, even after I stop all my sync jobs in the background, can you help me debug this? I only have 2 endpoints added, the S3drive official endpoint and my cloudflare R2 endpoint. And their used space are all relatively small, on has 80M of backup, on has 120M, and not many files, so I don't think file number or size should be a problem here. (One extra question unrelated, I find if I click close icon "x" on mac os, it will just quit the entire program(+status bar), but on my old linux machine, it is still running and visible on status bar, is this a mac specific problem?) (edited)

JourinT

After I updated to 1.13.0 on my M4 macbook air, I find it is constantly using around 15-20% of CPU in background, even after I stop all my sync jobs in the background, can you help me debug this? I only have 2 endpoints added, the S3drive official endpoint and my cloudflare R2 endpoint. And their used space are all relatively small, on has 80M of backup, on has 120M, and not many files, so I don't think file number or size should be a problem here. (One extra question unrelated, I find if I click close icon "x" on mac os, it will just quit the entire program(+status bar), but on my old linux machine, it is still running and visible on status bar, is this a mac specific problem?) (edited)

Thanks for your feedback.

After I updated to 1.13.0 on my M4 macbook air, I find it is constantly using around 15-20% of CPU in background,

In 1.13.0 release we've updated dependencies and app rendering engine: https://s3drive.app/changelog Can you see if minimizing app changes anything? Can you confirm that this issue hasn't existed e.g. in a 1.12.9 release?

(One extra question unrelated, I find if I click close icon "x" on mac os, it will just quit the entire program(+status bar), but on my old linux machine, it is still running and visible on status bar, is this a mac specific problem?)

This behavior will be fixed soon on macOS. It behaves differently, as there as some quirks between our app and OS integration. We use minimize library which apparently misbehave on macOS, so we'll need to do fixing ourselves. Expect improvement in that area in a next few weeks/months.

Changelog - S3Drive

Tom

Thanks for your feedback.

After I updated to 1.13.0 on my M4 macbook air, I find it is constantly using around 15-20% of CPU in background,

In 1.13.0 release we've updated dependencies and app rendering engine: https://s3drive.app/changelog Can you see if minimizing app changes anything? Can you confirm that this issue hasn't existed e.g. in a 1.12.9 release?

(One extra question unrelated, I find if I click close icon "x" on mac os, it will just quit the entire program(+status bar), but on my old linux machine, it is still running and visible on status bar, is this a mac specific problem?)

This behavior will be fixed soon on macOS. It behaves differently, as there as some quirks between our app and OS integration. We use minimize library which apparently misbehave on macOS, so we'll need to do fixing ourselves. Expect improvement in that area in a next few weeks/months.

Great to know

hasn't existed e.g. in a 1.12.9 release?

Can you give me a link to an older version? I don't remember seeing cpu breaking 10% on idle before, and within time of this problem this update seems to be the only factor, if you have the install package I can check to just make sure.

Can you see if minimizing app changes anything?

I am always keeping it minimized as I don't want to see it in the task switcher, so I think no. And also what I find is that when I first start the app, it is idling at 1-2%, it only went to around 15-20% after I put it in background for a while. Maybe after you give me the link to the older version I can turn on logging and run for a bit to see what happened when cpu usage went up. (edited)

Please find the link to previous release: https://github.com/s3drive/macos-app/releases/tag/1.12.9

1

Tom

Please find the link to previous release: https://github.com/s3drive/macos-app/releases/tag/1.12.9

Thanks for your help, I will report back later with logs from both versions.

Tom

Please find the link to previous release: https://github.com/s3drive/macos-app/releases/tag/1.12.9

Hi, tried 1.12.9, cpu is always <1%, so can confirm is a problem from 1.13.0(because it is start around 1% and goes up to 10% in 1-2 hours, but 1.12.9 has been <1% every time I check activity monitor in the last 3 hours), I will go back to 1.13.0 now and record some logs today and send it to you. (edited)

JourinT

Hi, tried 1.12.9, cpu is always <1%, so can confirm is a problem from 1.13.0(because it is start around 1% and goes up to 10% in 1-2 hours, but 1.12.9 has been <1% every time I check activity monitor in the last 3 hours), I will go back to 1.13.0 now and record some logs today and send it to you. (edited)

That's an useful finding, as it already narrows down list of things for us. Thanks! Quick question, once you start the app is the idle load already increased/higher (comparing to 1.12.9) or perhaps it does happen after some sync/upload/download operation? (edited)

Tom

That's an useful finding, as it already narrows down list of things for us. Thanks! Quick question, once you start the app is the idle load already increased/higher (comparing to 1.12.9) or perhaps it does happen after some sync/upload/download operation? (edited)

I have a sync task every 15 minutes, and the first try after opening is at 6 minutes, what I have observed:

At first, it idles around 1.1, 1.2% (it is idling at a higher cpu usage than 1.12.9, because 1.12.9 will go down into <0.5%)
After first 10 minutes(meaning it has done the first sync), it is at around 1-2%
after 5 minutes, it climbed to >2%, never goes down to 1% anymore
now looking at the time the experiment has been going on for 40 minutes, and it is idling around 3.4% now on cpu Note that sync mode is "copy", and between this experiment actually no files is ever modified in the directory.

(edited)

Now it has climbed to that 15-20% region, and I take a look at the logs, only watcher connected/disconnected, sync info, seems to have no errors or warnings recorded so far.

JourinT

Now it has climbed to that 15-20% region, and I take a look at the logs, only watcher connected/disconnected, sync info, seems to have no errors or warnings recorded so far.

Thanks for the update. In a 1.13.0 version we've implemented bottom transfer status, there is a process which monitors the transfer/progress update and updates text. Apparently it doesn't stop post sync/upload/download operation, we'll have that addressed in a next update. I am still not convinced that was the reason, as 15-20% is quite significant. We'll try to observe it on macOS. If by any chance you notice any pattern, that would also be helpful for us. Thanks for your input so far!

1

Tom

Thanks for the update. In a 1.13.0 version we've implemented bottom transfer status, there is a process which monitors the transfer/progress update and updates text. Apparently it doesn't stop post sync/upload/download operation, we'll have that addressed in a next update. I am still not convinced that was the reason, as 15-20% is quite significant. We'll try to observe it on macOS. If by any chance you notice any pattern, that would also be helpful for us. Thanks for your input so far!

Thank you as well for your quick response, I am reverting to 1.12 now until the new fix and I will report back the usage situation. Yeah I also find 15+% crazy... as my macbook is always cold to the touch, that's when I find the problem and saw in activity monitor. But at the same time although the cpu usage is constantly growing, it also never increases to more than 20%, the highest that I have ever seen past week is 18.4%, so I original thought there are some phantom processes for sync spawning all the way until the concurrency limits, that's why the first thing that I tried is to stop all sync jobs. (edited)

Hi @JourinT, By any chance would you be happy to try newest release? https://github.com/s3drive/macos-app/releases/tag/1.14.0 I can't promise that it addresses the issue fully, but it would be worth trying.

Release 1.14.0 · s3drive/macos-app

https://s3drive.app/changelog

Tom

Hi @JourinT, By any chance would you be happy to try newest release? https://github.com/s3drive/macos-app/releases/tag/1.14.0 I can't promise that it addresses the issue fully, but it would be worth trying.

Great and thanks, just installed, looks like it has a good start compares to even 1.12, I will keep on monitoring and report back (edited)

Tom

Hi @JourinT, By any chance would you be happy to try newest release? https://github.com/s3drive/macos-app/releases/tag/1.14.0 I can't promise that it addresses the issue fully, but it would be worth trying.

Hi, so far no more high cpu usage, I think we can safely regard this as solved. Thanks again for your help and wonderful app!