While you're here, please consider supporting GamingOnLinux on:
Patreon,
Liberapay or
PayPal Donation.
We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!



We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
Popular this week
- Is opening up your source code worth it? Terry Cavanagh thinks it was for VVVVVV
- Update your NVIDIA drivers due to multiple security issues found
- Looks like we may see Steam properly on Chrome OS by the end of 2021
- GNOME Shell to get an Activities Overview design revamp in GNOME 40
- The open source Epic Games Store app Heroic Games Launcher has a big overhaul
Contact
Latest Comments
-
What we expect to come from Valve to help Linux gaming …
- Liam Dawe -
Proton 5.13-5 is now up bringing in some of the experim…
- Tchey -
What we expect to come from Valve to help Linux gaming …
- stormtux -
What we expect to come from Valve to help Linux gaming …
- Duke Takeshi -
What we expect to come from Valve to help Linux gaming …
- gradyvuckovic - See more comments
Latest Forum Posts
- Forza Horizon alternatives for Linux
- Xpander - 3dmark Fire Strike benchmark
- The_Aquabat - Community livestream countdown
- Salvatos - New Desktop Screenshot Thread
- Xpander - Intel Xe vs AMD Radeon
- Dennis_Payne
Maybe it is not the right section to post this into, feel free to move, if needed.
Anyway,
In my system, steam takes quite a bit of system resources (cpu memory, gpu memory, sometimes cpu cycles).
Things are no way better since the introduction of the new library system since it seems everything now is done via the embedded browser, but I don't want to dig into how inefficient this could be.
Since my system specs are not stellar (only 3GB of video ram), i have to shut down the whole steam client when starting games which doesn't run from Steam.
(and for the games I start with the steam client, I just kill steamwebhelper processes; it somehow helps a bit, but this is not relevant now).
Question is in the topic, if I shut down the client, when I need to start it again, it takes something like a bunch of seconds (more than 10), even on an SSD. Of course i can live with that, but since my whole system starts in about the same time, i ask myself if there is some magic/hidden/locked switch i can use to make the client to start faster.
Thanks!
View PC info
I have 16gb or Ram and Ryzen 2600 and sometimes it takes quite a while also, but not always, I think that on my case it has something to do with the internet, maybe the client is trying to communicate to the servers and it can't do it, not sure. Also I found that if you leave the client on the front page of the store it uses more resources than leaving it on the library or the activity page.
View PC info
Thanks, definitely something to try, and thank you for the detailed explaination!
I'm waiting for the day you will need a browser based application to do 1+1=2.
Just wait and see :)
View PC info
For the full-size client, there's a “Low Performance Mode” in the settings, under “Library”. I found it helped a lot when they introduced the new library, although not with the startup speed. “Low Bandwidth Mode”, on the same page, might be worth a shot too. Although, as the name suggests, it's intended to save network bandwidth, anything that loads less stuff into memory will surely help.
Count yourself lucky you have an SSD. I'm still on spinning rust, and Steam takes the best part of a minute to start. I'll have to try that -noverifyfiles switch.