Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keka brings Mac to a crawl - MacOS Mojave 10.14.6 #436

Open
kubik101 opened this issue Aug 19, 2019 · 6 comments

Comments

@kubik101
Copy link

commented Aug 19, 2019

Hi I have been using Keka for many years.

Recently after I finally updated to Mojave I noticed that when I was extracting something in Keka that all other apps on my machine would slow down to a crawl.

I made sure Keka was updated to the latest version and still the machine runs super slow when extracting.

In Activity monitor Keka is only using 1 to 1.5 % CPU.

Symptoms:
Google Chrome: App opens but takes an incredible long time for a web page to load.
Safari: App opens and web pages open fine.
Photoshop: Almost impossible to open App. Sometimes it just hangs "Application not responding".

Please note the machine comes back to life after Keka has finished.

Specs of my machine:
iMac (Retina 5K, 27-inch, Late 2014)
Processor: 4GHz Intel Core i7
Memory 32GB

@issuelabeler issuelabeler bot added core web labels Aug 19, 2019

@aonez

This comment has been minimized.

Copy link
Owner

commented Aug 21, 2019

@kubik101

This comment has been minimized.

Copy link
Author

commented Aug 21, 2019

Sounds good.
How do I check if Keka is using “keka7zip” (p7zip) ?

@aonez

This comment has been minimized.

Copy link
Owner

commented Aug 21, 2019

@kubik101

This comment has been minimized.

Copy link
Author

commented Aug 30, 2019

This is what I see in Activity monitor:
Keka 0.2%CPU 0.36CPU Time 5 Threads
kekaunrar 7.5CPU 4.07CPU Time 1 Thread

My processor is in an iMac: 4 GHz Intel Core i7
Retina 5K, 27-inch, Late 2014
32 GB 1600 MHz DDR3

@aonez

This comment has been minimized.

Copy link
Owner

commented Sep 2, 2019

Keka 0.2%CPU 0.36CPU Time 5 Threads
kekaunrar 7.5CPU 4.07CPU Time 1 Thread

This seems pretty fine, less than 10% of the CPU used. Normally this is what happens on extractions. When compressing things change and it may use most of your CPU.

I'm working in a thread limit, so you can choose how much CPU to use per operation.

@aonez aonez added performance and removed core web labels Sep 2, 2019

@aonez aonez self-assigned this Sep 2, 2019

@aonez aonez modified the milestones: Look at, Random bag Sep 2, 2019

@aonez aonez added the works for me label Sep 2, 2019

@aonez

This comment has been minimized.

Copy link
Owner

commented Sep 5, 2019

@kubik101 you can indeed test the threads limit in the current beta version:

Screen Shot 2019-09-05 at 07 22 12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.