Element on Nostr: nprofile1q…gflvz nprofile1q…v0n4t the reason your synapse is using half a gig of ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq3ds9j6ycjxr0f6k40hvvqx6229q652y3avh3cu582k3kpgqk3vrqcgflvz (nprofile…flvz) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqzxn5thzmj2252w9dfyw3n5vcgjrajawp5uvpss3v3wk9m20q6zas9v0n4t (nprofile…0n4t) the reason your synapse is using half a gig of RAM is not because the workers are resource inefficient (are you even using workers?). core optimisation work for synapse will continue to be FOSS, and indeed $ from large scale Synapse Pro instances will hopefully fund that work.

To be clear: Synapse Pro is aimed squarely at huge server deployments and improves scalability. But core performance optimisations will still be FOSS.