WetGeek If your hibernate always (in all workspaces) un-hibernated successfully with the default Solus swap space, then I'm of the "if it ain't broke..." school of thought.
That said anything maybe just a modest bump to test?
I nuked my swap by accident rebuilding my filesystem recently and re-created my swap based upon a formula---but only to handle too many processes i.e., my reasons had nothing to do with sleep or hibernate.
I can't answer the question about the installer.
I'm wary of just matching it 100% right away. Maybe 25% increments, reboot, see what happens.
2 cents. Too much too quick has never been a good recipe on my older equipment. Baby steps has.
With the SSD dynamic (vs. the traditional hdd/ram combo) I think I'm starting to understand maybe.

      brent I'm of the "if it ain't broke..." school of thought

      First let me say that DataDrake is 100% right in suggesting that the swap space should be the same size as RAM. He needs to be sure that his advice keeps everyone who reads it perfectly safe in all cases. I would do the same in his position.

      I was trying to make sure I understand exactly how the hibernate function works in Solus, because I use it routinely. Now I know that it's the amount of RAM that's currently in use that matters, and I know how to check that. And I know that it's my responsibility to use that feature safely, and I'm okay with that.

          WetGeek Gotcha, I understand. It is the amount in use that matters, and that's what I learned as well about hibernate.
          On a related note, do you find having all those isolated work spaces an effective 'compartmentalization' as in more secure? Or just preference? I'm asking because I am interested in going towards compartmentalization in the future.

              brent do you find having all those isolated work spaces an effective 'compartmentalization'

              No, that's not why I use them (and would have preferred a couple more). I want to be able to have that many applications (as I listed in an earlier post) immediately available to me on a continuing basis, without having them stacked on top of each other. Thus, it's mainly a convenience.

                  WetGeek thanks for the reply, wetgeek. I like the non-stack/non-taxing approach. I might try it if the navigation is easy.

                      brent I might try it if the navigation is easy.

                      I'm sure you could handle it after a bit of training.

                          WetGeek My frame of references is I tried this (work spaces) when I had a (very) brief flirtation with Solus Gnome. Hopefully it's different in Budgie, looks-wise. Shall see.

                            brent I am interested in going towards compartmentalization in the future.

                            As happy as I am with Solus (and that hasn't changed at all), I routinely browse DistroWatch to see what's new. One thing I noticed today was EasyOS, based on Puppy. It made me think of you, because it provides the concept of "containers," in which a process can be run inside, or outside, of a container. The container gives each process its own copy of the / filesystem, so it's like a private sandbox. Lots of configuration available!

                            For me, it's not worth the time to download and install it, but I thought you might want to take a look because of your interest in compartmentalization.

                                WetGeek Browser compartmentalization is all I'm ready to try. Don't need a new OS for that, but thanks.

                                    brent Browser compartmentalization is all I'm ready to try.

                                    Then anything derived from Chromium (Chrome, Opera, Vivaldi, etc.) should do what you want. If you open several tabs, then go take a look at htop, you'll see that every tab represents its own process.

                                    For example:

                                    If you're looking for something else, please be more specific about what "compartmentalization" means to you, and more help will certainly appear.

                                        I meant, browser, I am sorry for being unclear. And browser compartmentalization has nothing to do, in my reading, with multiple tabs, but rather different browsers for different functions. Hence I was drawn to the work spaces idea as well, conceptually. I will also confess I have not read everything about it, but was asking as an aside. Thanks for your time on this, WetGeek .

                                        EDIT: I'm wrong as usual---the philosophy of containers is more what I'm interested in more than that general long c-word that I can barely spell. Please forgive me for mangling syntax--I was unclear.