Hi,
So we've rolled out composite 4.0 to about 15 users each with their own username/password and site as a small scale test. What we're finding is that when all 15 users are logged into the admin console and making changes to their site the Composite C1 Console hangs around 3 times every hour for each user at various points. The public facing websites are responsive but the console itself is unresponsive, it gets stuck on a screen and shows the mouse with a "spinner" next to it. They can work around this by closing their browser and re-launching the composite console.
Was composite designed to handle this type of use? Or was it only meant to have a handful of users editing a site at any one time?
Thanks,
So we've rolled out composite 4.0 to about 15 users each with their own username/password and site as a small scale test. What we're finding is that when all 15 users are logged into the admin console and making changes to their site the Composite C1 Console hangs around 3 times every hour for each user at various points. The public facing websites are responsive but the console itself is unresponsive, it gets stuck on a screen and shows the mouse with a "spinner" next to it. They can work around this by closing their browser and re-launching the composite console.
Was composite designed to handle this type of use? Or was it only meant to have a handful of users editing a site at any one time?
Thanks,