Tips Archives • Page 26 of 64 • Linux Tips

How To: Make Google Chrome Use Less RAM (UPDATED)

Today’s article is going to be a brief article about a previous article, where I gave you one way to make Google Chrome use less RAM. Consider this an updated article. So, if you’re trying to make Google Chrome use less RAM (and power, I guess) read on!

As tech goes, the situation has changed. As the tech changes, so too must we change our reactions to said changes. The thing with tech is that it never stands still, something that I (for one) appreciate.

The article in question is about making Google Chrome use less RAM. This applies to other browsers, but I concentrated on Chrome. Here is that article:

How To: Make Google Chrome Use Less RAM (And Other Browsers)

In that article, I recommended folks use the “Auto Tab Discard“ plugin. That recommendation has not changed. It’s a great add-on that will discard unused tabs, saving you both RAM and some power (which is useful for mobile devices).

Now, Google (along with other browsers) have enabled a new(ish) feature. Basically, to save power, the browser does what Auto Tab Discard does – it puts unused tabs to sleep. So, when you open those tabs that were sleeping you will need to wait a moment for them to reload.

That’s not a problem. The problem is, Google does this indiscriminately by default. Chrome does seem to make an exception for tabs that are playing audio or video, but all other tabs are fair game and will be put to sleep.

I repeat, all other tabs are fair game. They can and will be put to sleep. That’s downright annoying when you distinctly want to keep some tabs from going to sleep.

Fortunately, you have options.

You can disable this feature in your settings and continue using an extension like “Auto Tab Discard”. That’s a fine choice. That was my choice. It’s probably the wrong choice, but it is a choice.

Your other choice is to manually add sites to the whitelist, telling Google to keep those tabs open. So, you won’t need the extension if you choose to do it this way. This is probably the best choice. This is the choice I did not make.

I’ll show you how to make that choice, and kinda format this like a ‘regular article’…

Make Google Chrome Use Less RAM:

For once, you don’t need to open a terminal!

Instead, open Google Chrome. Then, click on the vertical three-dot menu in the upper right, and then you need to click on “Settings”. When that tab opens, click on “Performance” (on the left) and the rest should be fairly obvious.

If you’re like me, you can just disable the feature. That looks like this:

disable the power saving feature for Google Chrome — At this stage you can modify your settings as you see fit. I’ve turned the feature off. Go me!

If you want, you can keep the feature enabled (it was enabled by default at my house) and just add your favorite sites to the list of sites that always remain active. I don’t feel like messing around with it, so I’ve simply disabled the feature and opted to keep the extension.

I suppose that might mean I use a little extra RAM, I haven’t tested but it’d be a very trivial amount and I quite like the GUI offered by the installed extension. When I next do a clean install, I’ll probably just let the browser deal with it instead of using the extension.

Other browsers may use similar tactics to save power (and free up RAM, the two are related). As of the time of this publication, this was not yet a feature that’s in Google’s opensource counterpart Chromium. Right now, this appears to just be a function in the proprietary version, but tech changes and that too may change.

Closure:

And, well, now you can see why this is an article all of its own. It was more than I could reasonably add as an update to the existing article and was enough information to make a new article. After publication, I’ll update the previous article to link to this article. I hope… Hopefully, I remember to do that.

Hmm… I think I forgot to do a ‘meta’ article in February. February is a pretty short month, plus I’ve been otherwise distracted. But, I’ve not been too distracted to skip a publication date! We’re rapidly approaching the two-year mark. It has been a pretty good ride!

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Let’s Let AI Write An Article About ‘sed’

Today’s article is going to be about ‘sed’. However, I’ll be letting AI write it, just so we have an excuse to play with ChatGPT. I love new tech and I’m going to go against the advice given and just post the resulting article directly.

Also, I picked ‘sed’ as an article topic because it’s a pain in the butt to explain even the basics. It’s such a powerful tool that knowing where to start can be tough. As such, I’ve decided it’s a perfect article for testing AI. I will only be formatting the suggested article.

Hey, it was this or write a meta article. I hadn’t written one for February and this will be the last article in February. Not much had changed, though we did cross some milestones, and I figured this article would be even more interesting to my readers.

Again, if there are errors, I am not to blame. I am posting the entire output after asking ChatGPT to write the article. I am only editing for the format. So, read on to see how AI is coming along. Hint: It’s doing well! It’s coming along nicely!

About ‘sed’:

“sed” is a stream editor in the Unix-like operating systems. It is used to perform basic text transformations on an input stream (a file or input from a pipeline). The sed command reads the specified files, or standard input if no files are specified, and applies the transformations which have been specified.

The syntax for using sed is:

sed [OPTIONS] 'COMMANDS' [INPUTFILE(s)]

1	sed [OPTIONS] 'COMMANDS' [INPUTFILE(s)]

Where OPTIONS can be any of the options available in the man page and COMMANDS are the instructions that tell sed what transformations to perform on the input.

One of the most common uses of sed is to replace strings. The basic syntax for string substitution is:

sed 's/old-text/new-text/' [INPUTFILE(s)]

1	sed 's/old-text/new-text/' [INPUTFILE(s)]

Where old-text is the text you want to replace, and new-text is the text you want to replace it with. For example, to replace the word “apple” with “banana” in the file “fruits.txt”, the following command could be used:

sed 's/apple/banana/' fruits.txt

1	sed 's/apple/banana/' fruits.txt

You can also use regular expressions in the old-text argument to match a more complex pattern. For example, to replace all occurrences of “apple” or “Apple” with “banana”, the following command could be used:

sed 's/\(apple\|Apple\)/banana/' fruits.txt

1	sed 's/\(apple\\|Apple\)/banana/' fruits.txt

Another common use of sed is to delete lines. To delete a line, you can use the d command. For example, to delete the first line of the file “fruits.txt”, the following command could be used:

sed '1d' fruits.txt

1	sed '1d' fruits.txt

To delete multiple lines, specify the line numbers separated by a comma. For example, to delete lines 1 to 3 in the file “fruits.txt”, the following command could be used:

sed '1,3d' fruits.txt

1	sed '1,3d' fruits.txt

sed also supports multiple commands in a single execution. Simply separate the commands with a semicolon (;). For example, to delete the first line and replace “apple” with “banana” in the file “fruits.txt”, the following command could be used:

sed '1d;s/apple/banana/' fruits.txt

1	sed '1d;s/apple/banana/' fruits.txt

In addition to the commands mentioned above, there are many other powerful commands available in sed, such as inserting text, printing selected lines, and more. To learn more about these commands and other features of sed, consult the man page by running man sed in your terminal.

In conclusion, the sed command is a useful tool for performing basic text transformations on files or input from a pipeline. Its syntax is straightforward, and its wide range of commands makes it versatile enough to handle a variety of text manipulation tasks.

Closure:

There you have it. You have an article about sed – and it wasn’t written by me. So, what do you think of it? Do you think I can hang up my hat and just let AI write my articles from here on out? Do you spot any mistakes? It’s supposed to be an overview, not a complete dissertation. I think it does surprisingly well!

How To: Show Your Network Interfaces

Today’s article will be fairly simple, where we learn a couple of ways how to show your network interfaces. It won’t be a very long article, nor will it be all that complicated. Like almost always, today’s article will involve the terminal. So, if you want to learn how to show your network interfaces, read on!

A network interface is what’s used to connect your computer to a network. Depending on your configuration, you may have both real and virtual network interfaces. The real network interfaces will be things like your ethernet (the wired connection to the network) and a wireless device (a radio-controlled network interface).

There are times when you’ll want to know your network interface, be it for debugging or monitoring. For example, you’ll probably want to know about your network interfaces if you’re playing around with VNStat.

We’ve probably touched on this subject in a few articles. However, we might as well have an article specifically answering the question of how to show your network interfaces. Well, then, that’s what this article will cover.

Show Your Network Interfaces:

As mentioned in the intro, we’re going to be using the terminal. If you’re a regular reader, you’re probably used to it and a little tired of the same old text. Not all my readers are going to be as proficient, so they should know that they can just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, your next step mostly depends on your chosen distro and the age of the default installed tools. If you’re using an older distro, you can go with this command:

ifconfig -a

1	ifconfig -a

If you’re using a distro with more current tools, you will likely find that ‘ifconfig’ has been deprecated, that is no longer current and in use. For you folks, you’ll need a slightly longer command:

ip link show

1	ip link show

So, if you want to show your network interfaces, one of those two commands will likely get you there. You should check the information carefully, to make sure you’re using the correct information, such as when you want to use a network interface name for another command.

Closure:

There you have it… You have another article! This time, we’ve decided to spend some time learning how to show your network interfaces. It’s nothing complicated, but it’s still useful information. It is indeed a fairly short and simple article, but that means newer users can follow along – which is a good thing. I’m sure there are other ways to gather this information, but one of those two commands should do the trick!

How To: Return To The Previous Working Directory In The Terminal

Today is another easy day, but one that should be productive, where we’ll learn how to return to the previous working directory. It will be a short article, but you might find it useful. If nothing else, we’re making the more terminal accessible to new users.

These Linux tips needed to be shared some time, so it might as well be now. I don’t wish to air my medical issues, but my ailment has gone on long enough and I went to a medical professional this morning. I’m sure I’ll be fine. They say only the good die young, so I’m probably gonna live forever!

Anyhow, to learn how to return to the previous working directory (in the terminal, of course), read on! I promise, it’s easy. It’s one simple command and that’s all there is to it.

Return To The Previous Working Directory:

This article requires an open terminal, like many other articles on this site. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

This is probably more useful for very-nested directories with long names, but it won’t take that to demonstrate today’s subject. It’s not terribly complicated.

Let’s say that you’ve navigated to ~/foo and performed some functions there. Next, you’ve navigated to ~/bar and performed some functions there. Now, if you want to return to the ~/foo directory you can do so with just a simple – added to your cd command, like so:

cd -

cd -

If that’s confusing, I’ve made an image that explains it better than I can…

use cd - to return to the previous working directory — It’s a simple concept. It’s a simple article about how to return to the previous working directory.

See? It’s nice and simple! If you were in one directory and left to go to a new directory, then it’s trivial to return to the previous working directory. The image should help make it clear if my description is lacking.

Closure:

I know… I know… This is a lot of short articles in a row. I’ll feel better. I’m sure of it! Amusingly, I was asked if I had any stress in my life and it was comforting to answer that I do not. My life is pretty drama free, but I do need to get an article out every other day! This time, I’ve shown you a quick and easy way to return to the previous working directory. It’s quick, easy, and effective!

Navigate To The Start Or End Of The Line (In The Terminal)

Today is going to be another simple article, where you learn to navigate to the start or end of the line – in the terminal, of course. I’ve had some abdominal issues, so it seems like a good day for yet another accessible article.

Even though it’s an easy article, there will be many Linux users who don’t know this information. I’m not even sure how to describe it, thus the unwieldy article headline. So, if you want to navigate to the start or end of the line in the terminal, I’ll show you how.

This being Linux, there are so many ways to do this sort of stuff…

Imagine this:

You’re using Ubuntu and you want to update from within the terminal. So, you’ve typed the following:

sudo apt update && sudo apt upgrade -y

1	sudo apt update && sudo apt upgrade -y

Well, as you can see, the first instance of ‘sudo’ was spelled wrong – it’s missing a letter. You can reach over there and find the arrow buttons, navigate back to the start of the line, and fix it. Or, you can do the following:

Navigate To The Start Or End Of The Line:

As the title indicates, this is in the terminal. As such, you’ll need an open terminal to try this out. Just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, why don’t we just use that line from above:

sudo apt update && sudo apt upgrade -y

1	sudo apt update && sudo apt upgrade -y

Of course, you could just look at your keyboard and (probably) use the HOME button to navigate to the start of the line. Of course, you could then use the END button to navigate to the end of the line. If you’re on a laptop, those keys can be placed most anywhere, though it’s far more standardized with a regular keyboard.

But, you don’t have to reach for those lines. Nope. That is not necessary. You can keep your eyes right on the screen. How so?

Well, it’s this easy:

To navigate to the start of the line, press CTRL + A.

To navigate to the end of the line, press CTRL + E.

Tada! You don’t have to root around for the home or end buttons. You don’t have to fuss with the arrow buttons. You can quickly and easily navigate to the start and end of the line with just those two keyboard shortcuts. I told you that it’d be quick and easy!

Closure:

There you have it, you have another article. This one is pretty simple but that’s okay. So long as it’s sharing some knowledge and I managed to get an article out on schedule, it’s all good by me. This time, you’ve learned how to navigate to the start of end of the line – in the terminal and without taking your eyes off the screen.

You might as well memorize the shortcuts as they appear to be pretty universal from my testing. They’ll likely be faster for you than any of the other methods, so they’re worth learning and adding to your growing toolbox of Linux tools. Ideally, my ailments will go away soon… I’m hopeful…