Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization

Before announcing some new exciting features for the users lets talk about the big incoming change for the admins in #Movim 🧑‍💻✨

Movim used to have a "one user = one php worker" policy. The sourcecode was fully refactored to isolate user sessions in those workers allowing worker to host several users!

This is the biggest architectural change in Movim since its full real-time rewrite of 2014 🤯

The goal of this change is simple: by having several users / worker most of the "Movim code" is shared, lowering the memory usage.

We are testing a 4 users/worker policy. Which saves 75% of RAM, pretty neat no?

There is still some quirks to fix, but it's coming soon 👀

#xmpp #memory #optimization