Bug 378118 - ktouch is unusable slow at older system (ThinkPad T61)
Summary: ktouch is unusable slow at older system (ThinkPad T61)
Status: RESOLVED DUPLICATE of bug 350336
Alias: None
Product: ktouch
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: Sebastian Gottfried
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 18:37 UTC by ulr_bugs_kde_org
Modified: 2017-03-31 17:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ulr_bugs_kde_org 2017-03-26 18:37:07 UTC
Hello,

ktouch is the best typing tutor I know. I used it myself and now I wanted it to help my daughter. But unfortunately it takes a long long time until one can see the typed letters. This makes it unusable slow. It takes much cpu resource.

I expect: A typing tutor should not be very cpu consuming. It should be usable also on older machines.

I have a ThinkPad T61 and use debian testing.

I would like to help finding the reason. But therefore I would need some  	instructions. No problem to translate the program (using make) or possibly edit some cpp files. But I'm not used to work with profilers or something else to analyze run time behavior.

Best regards,
Ulrich
Comment 1 Sebastian Gottfried 2017-03-26 20:39:51 UTC
Which version are you using? 2.x oder 16.12.x?

The older version has a major performance bug. For this version you have to apply the patch from Bug 346248 and compile the app yourself. But then you could also just install or compile the latest version which should have very little CPU usage. On my system (Intel Sandy Brigde) I can't get over 10 % CPU usage.
Comment 2 ulr_bugs_kde_org 2017-03-27 03:53:31 UTC
Hi,

now I know, that I have the older version 2.3.0. The patch from bug 346248 solves the problem.

Thanks a lot.
Comment 3 Christoph Feck 2017-03-31 17:31:06 UTC

*** This bug has been marked as a duplicate of bug 350336 ***