Scaling issues #30

New issue

Open

opened 2022-11-25 09:42:23 +00:00 by creiss · 1 comment

creiss commented

2022-11-25 09:42:23 +00:00

Member

Hey! :-)

I am running a 200+ Relay server, and the one-threadded design is reaching its limits.
It would be better to allow scaling to enable clustering.

HaProxy on front, several backends. Each backend is a redis cluster memmber and all informations (joined servers, pushed notifications, certificates) are pushed into the redis. Redis could become non-volatile.

Or of course, any other way that seems practicable. But keeping this software on a single core hinders growing.

Hey! :-) I am running a 200+ Relay server, and the one-threadded design is reaching its limits. It would be better to allow scaling to enable clustering. HaProxy on front, several backends. Each backend is a redis cluster memmber and all informations (joined servers, pushed notifications, certificates) are pushed into the redis. Redis could become non-volatile. Or of course, any other way that seems practicable. But keeping this software on a single core hinders growing.

izalia commented

2022-11-25 19:00:16 +00:00

Member

Basic multi-threading support was added in the dev branch with 9839da90 which should help a bit. Clustering is definitely a good idea though and I'll look into it in the near future.

Basic multi-threading support was added in the dev branch with 9839da90 which should help a bit. Clustering is definitely a good idea though and I'll look into it in the near future.

No labels

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

pleroma/relay#30

No description provided.

Rows
Columns