seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

Issue on a multi-core system #459

New Issue
Open
opened 2018-06-25 16:29:42 +02:00 by truhlikfredy · 0 comments
truhlikfredy commented 2018-06-25 16:29:42 +02:00 (Migrated from github.com)
Copy Link

On a 4 core system the load is pretty minimal, but on a larger workstation, it's spreading to all cores and accumulatively take plenty of resources. Is there a way to limit how threads it will use as I have a feeling now it's probably oversaturated.

screenshot_20180625_152532

On a 4 core system the load is pretty minimal, but on a larger workstation, it's spreading to all cores and accumulatively take plenty of resources. Is there a way to limit how threads it will use as I have a feeling now it's probably oversaturated. ![screenshot_20180625_152532](https://user-images.githubusercontent.com/1096073/41856150-4801381c-788c-11e8-9722-ad2f13aa4107.png)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#459
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?