Google Chrome uses multiple processes at once as part of its ordinary operation, and all the processes that you're seeing listed are Google Chrome. When you do more with the browser, more will appear. Processes will also terminate during the normal course of using Google Chrome. Which process or processes you will be interested in monitoring depends on why you are monitoring them in the first place, but if you want to see what resources Google Chrome is consuming, then you will likely want to look at all of them.
The Chromium and Google Chrome browsers use multiple processes for things that most browsers use multiple threads in the same process. Although there is a main "browser" process that creates the browser's own user interface, accesses data on disk, and communicates over a network, this isn't necessarily the process that will be using the most CPU or memory resources. More often than not, creating a new tab and navigating to a website creates a new process, and closing such a tab terminates the process.
Chromium and Google Chrome use the boundaries between processes, provided and enforced by the kernel of the operating system, as a form of sandboxing to maintain higher security and stability. For example, separate processes cannot easily read and write one another's memory, while different threads in the same process may easily do so.
As for how you will go about examining all these processes, that depends on what you are actually looking for. But if you are interested in how many CPU cycles are used and how much memory is consumed, this will likely be spread across the different processes. You can use
htop to examine this. (Your system should provide a
top command; the
htop command, you'll probably have to install, but some users prefer its interface.) You can list processes in real time by CPU, memory consumption, or usage of other resources. Many systems also have graphical programs that serve this purpose.
If you are interested in disk usage, that might be largely confined to a single process, but I still suggest examining all of them. If you are troubleshooting unexpectedly bad performance, it's useful to avoid unnecessary assumptions. In particular, plugins typically run in separate processes, and I believe some of those may directly access the disk.
top may provide you with some useful information about disk usage, on some systems. You haven't said what OS you're running, but the format that
ps uses for output suggests you might be running GNU/Linux. On GNU/Linux systems like Fedora, CentOS, Debian, and Ubuntu, I often find it beneficial to install and run
iotop to see disk usage. Usually it must be run as root (e.g.,
Similarly, for network usage, you may find it useful to install and run