On 17 November 2017 at 01:18, Ed Greshko <ed.greshko(a)greshko.com> wrote:
[...]
I suppose you need to start by using "top" or a similar utility to see what
process
may be taking up resources.
I second the idea of using top to find out what's eating up those
resources, otherwise you're shooting in the dark.
One other idea, is to check using a new user account; this way you
know if it's something specific to your account or a system-wide
issue.
--
Ahmad Samir