Mac OS works a little differently than Windows in this regard. It is much happier to find ways to "use" the RAM that exists on the system, regardless of how critical the data that it's storing in RAM actually is.
A workload that used 6GB of RAM on an 8GB Mac could very easily wind up using 10GB of RAM on a 16GB Mac. Based on usage alone, it's difficult to really tell how much active working memory is actually required for acceptable performance. Memory Pressure is a much better metric on Macs and gives a clearer picture of how heavily the memory is actually used.
(On the Unified Memory Architecture, GPU processes from Chrome, etc will be listed separately from the main process and it will appear as though they both have their own independent pools of memory. If you click on the process on Activity Monitor, it will show how much of that RAM is actually shared between the parent process and the GPU process. In Chrome's case, the majority of that memory is usually shared, and the UMA does a good job of preventing it all from needing to be allocated twice. You can also see metrics such as "real memory size" which shows how much actual physical RAM is being occupied by the process after the compressor and swap have done their jobs).
It is worth noting that Apple Silicon Macs apparently do memory compression in hardware now (at least based on reports that examined the A14 and the M1). This is a huge improvement over the Intel based macs, and means that the performance hit will certainly be smaller than it was in the past. I've found that the new Macs can generally handle workloads that push the memory pressure into the yellow more easily than the old Intel Macs could.
Swap, however, is a different story. DRAM latency is about ~300 CPU cycles, whereas swap can be estimated to be around about 300K to 1mil cycles. In other words, swap is plenty fast if it's just swapping out inactive memory from various apps and browser tabs you haven't looked at for hours. But as soon as it starts swapping heavily (and memory pressure enters the red), it's going to take a major performance hit.
How much RAM is enough? If you're just browsing the web and editing documents, 8GB is plenty (I do software development on an 8GB Mac, and you'd be surprised how well Mac OS can handle tight memory constraints). But applications also get heavier with time, and 8GB is on the lower end these days. You'll be happy with either, but if you have the extra money to spend, 16GB is definitely more future proof in the long term.