Abdelaziz Mokhnache

Firefox vs Chrome: Memory usage

60 | Published 17 Dec 2018 61 | 3 min. read 62 |

Chrome vs Firefox image

66 |

At the end of 2017, Mozilla introduced Firefox Quantum the blazing fast, completely reinvented Firefox. It was shipped with a new beautiful look and the speed compared to it’s previous versions was obvious. One of Mozilla’s claims too was the less usage of memory compared to Google Chrome. For a Firefox user like me, this was great news. I was able to notice the speed and enjoy the new design. But, I didn’t pay attention to how it compares to Chrome in memory usage.

67 |

Recently I read a blog post saying that Firefox consumes more RAM than Chrome. This was not what Mozilla claimed a year ago, I felt betrayed. I started searching for other blog posts with other benchmarks. But, I found different answers with different results. So, I decided to do my own tests.

68 |

Making some tests

These tests are made in the following environment.

69 |

OS: Ubuntu 18.04
RAM: 8 GB
Firefox: 64
Chrome: 70

70 | 71 |

After closing all the third party applicatins on my computer, I opened the Ubuntu System Monitor to see how much memory was in use. The initial memory usage was:

72 |

1	memory: 2.1 GiB

73 | 74 |

Then I opened 30 tabs of 3 different websites in each browser while the other is closed. I used the Guest Mode in chrome and the Safe Mode in Firefox ( by going to menu > help > Restart with add-ons disabled) in order to get rid of any effects of installed add-ons.

75 |

The opened tabs was the following:

76 |

Test 1: The 30 top answers of Jon Skeet on Stackoverflow.
78 |
Test 2: The 30 first pages of HTML tutorial on w3schools.
80 |
Test 3: 30 Quasar-framework components’ documentation pages (Field > Dialog).
82 |
Test 4: 20 different websites from the most famous ones (google, youtube, medium …etc).
84 |

86 |

Results

After the complete loading of the 30 tabs each time, I was opening the System Monitor to see the total memory usage. knowing the total memory makes it easy to deduce the consumption of each browser. It is as easy as subtracting the initial value of used memory from the new one (I calculated it this way because Chrome opens a lot of processes in Ubuntu and it is hard to keep adding them up). The consumed memory values corresponding to each browser are shown in the table below.

87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 |

	Firefox	Chrome
Test 1	1.0 GiB	1.3 GiB
Test 2	1.3 GiB	2.7 GiB
Test 3	1.2 GiB	2.1 GiB
Test 4	0.9 GiB	1.3 GiB

116 |

Summary

The results above demonstrates that Firefox Quantum really uses less memory than Google Chrome, at least in my case. That supports Mozilla’s claims about it’s new kid. I shared here the results I got. But, I can not garantee that everybody else will get the same thing. Concerning the speed, I didn’t make a real comparaison between the two. They are comparable in speed and I could not notice any difference in usage. Firefox nowadays is not the same Firefox couple of years ago.

117 |

How to create a node.js CLI and publish it to NPM

60 | Published 26 May 2019 61 | 7 min. read 62 |

node-cli

66 |

The toy programming language that Brendan Eich created back in the 90s, has became recently one of the most powerful and popular programming languages in the world. One of the big reasons that led to that progress is the invention of Node.js in 2009 by Ryan Dahl. Node.js and its large package management system NPM took Javascript from just being a simple scripting language for web browsers to be a full featured language that runs everywhere and helps building all kinds of cool pieces of software.

67 |

In this article, we will see together how to create a basic node.js CLI and share it with the world using NPM.

68 |

Let it be simple

The CLI that we are going to build is the simplest CLI that could ever exist. We don’t need to spend our energy building a complex one, because we have more important things to discuss. All what our CLI will do is taking a name and printing Hello {name}, welcome to node.js! to the console, as shown below.

69 |

1 2	$ hello Mohammed Hello Mohammed, welcome to node.js!

70 | 71 |

Let’s make it

First, let’s make a folder called hello. Inside it, let’s create a cli.js file that will contain all our code. Yes of course! you can name it as you want as long as you stay consistent with the name you chose. Here is all the code we need to be written to cli.js.

72 |

1
2
3

// cli.js
let name = process.argv[2];
console.log(`Hello ${name}, welcome to node.js!`);

73 | 74 |

let’s now run the script by typing node cli.js Mohammed and there you go. You should get Hello Mohammed, welcome to node.js! printed to the console.

75 |

1 2	$ node cli.js Mohammed Hello Mohammed, welcome to node.js!

76 | 77 |

In case you are wondering what process.argv means, it is simply an array that contains all the options that are passed in the command line when excuting the script. The first element of the array argv[0] is the path to the node command in the filesystem, the second argv[1] is the path to the script file path/to/cli.js that we want to execute while the third argv[2] is the name that we want to print.

78 |

Great, the script now is printing the message that we are expecting. But, Didn’t we say above that the usage should be hello {name} not node cli.js {name}? Yes, we did. And this is what we are going to do together right now.

79 |

It is just Shebang not Magic

Have you ever seen this comment #!/usr/bin/env node at the very top of a Javascript file and wondered what this is for? We all were in the same situation. This is called the Shebang. It is a comment that tells the Operating System what interpreter to use for this file if it is ran as an executable. We need to add it to the very top of our cli.js.

80 |

1
2
3

#!/usr/bin/env node
let name = process.argv[2];
console.log(`Hello ${name}, welcome to node.js!`);

81 | 82 |

This means for the OS that this file should be executed using the default node.js version installed on your system (the version that you get by typing node in your terminal).

83 |

Please give it a name

At this moment it is time to turn our CLI to an NPM package. All we need is creating a package.json file that will contain information about the package. You can create it manually or automatically using npm init -y command (feel free to modify the default properties as you want).

84 |

The last step is telling NPM the command’s name that we want to use. As we said before we want to replace node cli.js {name} by hello {name}. To achieve this, we simply add a bin property to package.json that contains the command’s name and the corresponding file to execute.

85 |

//package.json
"bin": {
  "hello": "cli.js"
}

86 | 87 |

By reaching this point, our CLI is finished and it is ready to be published on NPM. But first let’s test it locally to see if everything is working as expected.

88 |

Test it locally first

To test the CLI locally we need it to be installed globally, so the hello command will be available everywhere. But we haven’t publish it yet, how can it be installed globally? Here we need to run the npm link command.

89 |

1 2	cd hello npm link

90 | 91 |

when you run this command inside a package folder, it will make it available in the global scope as if it was installed with the -g flag.

92 |

Now, let’s test the CLI by typing hello {name}. Note that you can run hello from any location on your system, you are not limited to the package folder.

93 |

1 2	hello Mohammed Hello Mohammed, welcome to node.js!

94 | 95 |

Congratulations!! You’ve made your first node.js CLI. If you want to publish it to NPM and show it to the world, you’re almost there.

96 |

Publish it to NPM

This is the easiest part as you may not expected. First, you need to create an account on npmjs.com. Then login to it from you terminal using npm login.

97 |

$ npm login
Username: npmuser
Password:
Email: (this IS public) npmuser@gmail.com
Logged in as npmuser on https://registry.npmjs.org/.

98 | 99 |

It will ask you for your username, password & email and you should provide the correct credentials. Once you are logged in successfully, you will be able to publish your CLI and share with the world by running npm publish from the package folder.

100 |

1 2	cd hello npm publish

101 | 102 |

If there is no NPM package already published which have the same name as yours, after some second you can see your package live. Otherwise, you have to change the name property in package.json to an available value.

103 |

Now, everyone on planet earth with access to internet can install your package using npm i -g {yourPackageName} and execute it on there own machines. Thus, you’ve made your first contribution to a big and awesome community. Finally, don’t forget to share your code for good.

104 |

Blog

Blog

Blog

Blog

Blog

Abdelaziz Mokhnache

Flex Generator

vscode-quasar-snippets

ndarray-imhist

gnuplot-imshow

plotbd

ndarray-entropy

ndarray-corr2

Firefox vs Chrome: Memory usage

Making some tests

Results

Summary

How to create a node.js CLI and publish it to NPM

Let it be simple

Let’s make it

It is just Shebang not Magic

Please give it a name

Test it locally first

Publish it to NPM