Composite C1 is intended for this use scenario, but there are a few settings worth focusing on when you have intensive use of the C1 Console.
Edit ~/App_Data/Composite/Composite.config and locate the setting broadcastConsoleElementChanges="true" - change this to false and restart the app (In the C1 Console select Tools | Restart Server).
This will prevent every console to be forced to update affected tree structures every time en element is added, deleted or renamed. The drawback to prevent element change updates is that you wont see a new element someone else added, before you actively refresh or open the affected branch.
If you still experience performance issues I suggest you migrate to SQL Server - there is a package which does this without much fuss, see https://www.composite.net/Add-on-Market/Packages/Composite.Tools.SqlServerDataProvider
But judging from your description changing broadcastConsoleElementChanges will fix your issue.
Edit ~/App_Data/Composite/Composite.config and locate the setting broadcastConsoleElementChanges="true" - change this to false and restart the app (In the C1 Console select Tools | Restart Server).
This will prevent every console to be forced to update affected tree structures every time en element is added, deleted or renamed. The drawback to prevent element change updates is that you wont see a new element someone else added, before you actively refresh or open the affected branch.
If you still experience performance issues I suggest you migrate to SQL Server - there is a package which does this without much fuss, see https://www.composite.net/Add-on-Market/Packages/Composite.Tools.SqlServerDataProvider
But judging from your description changing broadcastConsoleElementChanges will fix your issue.