I don't know if I'm missing something, but please take this with a grain of salt.
So, zram is used to reduce I/O operations on the disk by making a swap on the memory which eliminates system freezes for users with HDDs and also 'increasing' the amount of data you can put on the memory. But the downsides is that once you run out of this swap, you will lose the speed advantage and have to swap to the HDD normally which could also swap out active pages instead of sending off LRU (least recently used) data. So it just works blindlessly by trying to compress everything thrown at it.
However, zswap tries to be smarter and does what zram does but requires more I/O activity. It caches the pages that are to be swapped and once the memory pool is full it swaps the least recently used pages. But it sends incompressible data straight to the disk swap.
Now here's the question, hear me out. Wouldn't increasing the memory pool size of zswap make it equivalent to zram by adding much more available space to the RAM by allowing the RAM pool to compress much more data and be able to accept more pages before getting exhausted WHILE ALSO keeping the smart characteristics of zswap like disk caching and swapping out LRU pages? Wouldn't this be the best of both worlds?
The only downside of this is that it'd still send off incompressible data to the disk which results in disk activity. I'm not sure about this but wouldn't decreasing swappiness to 1 get rid of this issue? Or does swappiness only affect inactive pages but not pages that zswap wasn't able to compress? If so, can anybody suggest a solution to this?