Conversation
Notices
-
@moonman !loadaverage is running on an HDD and 4G of RAM %).
We don't have Qvitter though, this may be the key resource-eater for the GNU social installations out there.-
@xrevan86 @moonman HLA has never really had performance problems, even with Qvitter, and LA's VM was copied from this instances (same specs).
It really comes down to optimising your database. Database use is the primary bottleneck. This is why optimising the joins like you did Alexei gave you the gains you got. You're hitting the database 100,000s of time in a minute if you federate with much people at all. -
Using the redis queue is the huge improvement it is, specifically because it greatly reduces the time for common queries to static information.
-
That said Redis has always been unreliable in the sense that every update breaks banana, so I might consider alternatives, or homebrew a caching thing, when I get that far.
-
@xrevan86 No, it is a memory-based cache unless you tell it specifically to page to the drive (which you can do, but it is not so by default)
-
