Language Selection

English French German Italian Portuguese Spanish

3 Reasons Why Your System Might Be Slow

Computer users expect their systems to work well at all times, but unfortunately this isn’t always the case. If your system becomes slow, there certainly is something you can do about it. This article will help you understand what’s happening on the system, whether it’s the computer in front of you or a system you’re accessing remotely.

When we say the system is slow we mean that it isn’t responding to our input in a reasonable time, or taking too long to complete a task. This can happen when there is *another* program using too many system resources, starving *your* program of resources, causing it to run slowly

There are three common ways in which this can happen, and all three of these scenarios can be equally crippling and put your system into a state where it seems to be frozen.

A program is monopolizing the cpu.
A program is using all of the cpu cycles, blocking access to the cpu to other programs. This may be intentional (programs that do heavy processing) or accidental (programs get stuck repeating something over and over).

You’re nearly out of physical memory.
You are either running too many programs, or programs that use too much memory. Your physical memory is almost entirely exhausted, and the running programs are using the harddisk as fallback memory, which is very slow.

A program is doing heavy I/O.
You may be copying a large file, for instance. The program that is doing the copying is requesting lots of data from the harddrive, but while it’s doing this the cpu is actually waiting for this data to be read from the harddrive, blocking access to other programs.

More Here




More in Tux Machines

Red Hat News

Fedora: The Latest

  • Korora 22 Flash Update
    As we announced when Korora 22 was released, Adobe Flash is no longer included by default.
  • Fedora repository for Doom stuff: Zandronum, Doomseeker, CnDoom
    I had a bit of free time over the last few days, and looked at the current state of the art for Doom on Linux. The awesome Rahul Sundaram has been looking after several Doom-related packages for a while – including the Chocolate Doom package – but there are some things that seem to be commonly used these days that we didn’t have packaged. So I packaged them up, and put them in a new repository!
  • CUDA 7.0 enabled programs for Fedora 22
    I’ve udpated the CUDA version in the Fedora 22 Nvidia repository, it now contains CUDA 7.0.28 along with the cuFFT 7.0.35 patch. Note that from this version, CUDA is x86_64 bit compatible only, so there are no more i386 packages. There is still the cudart library available for 32 bit, but I don’t think it’s worth packaging.
  • Secure Boot — Fedora, RHEL, and Shim Upstream Maintenance: Government Involvement or Lack Thereof
    Note that there are parts of this chain I’m not a part of, and obviously linux distributions I’m not involved in that support Secure Boot. I encourage other maintainers to offer similar statements for their respective involvement.
  • Remi repository is changing
    The "remi" repository exists for > 10 years, it have changed a lot, and some recent changes worth to be explained.

Android Leftovers

Leftovers: OSS