Language Selection

English French German Italian Portuguese Spanish

Fedora Day Four: Performance

Filed under
Linux

So I’m now a few days into my time with Fedora, and things are going well so far. The machine is all up and running, and I’m back at my keyboard working away. We now know how to make Fedora look good, but how well does it perform in practice? Let’s take a look…

System resources

As many people reading this will already know, neither Fedora, or Gnome-Shell are ‘light’ systems. But I don’t really understand why so many people within the Linux community love these light systems so much. I mean, a semi-modern machine now will have a dual-core CPU and at least 4GB of RAM. Not to mention the fact that SSD’s are becoming commonplace on machines now.

On my machine I currently have Chrome with six tabs open, thunderbird, and a couple of background apps like Copy.

rest here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more