Skip to main content

Replied to a post on github.com :

Without actually benchmarking it on a Banana Pi I'd say it's almost certainly infrastructure rather than code.

*probably* memory, or lack thereof, with the apache and or mysql processes.

While the datamodel, like elgg, is designed more for flexibility than raw speed, it should be able to easily handle 28000 posts. Especially when generally Known sites have far more reads than writes - it tends to be concurrent active writes, with the corresponding index updates that kills performance on databases, although even that is less of a problem with modern database engines.