Number of users supported by SugarCRM

[marcu]

Hello everybody,

I am interested in the number of users that can use simultaneously SugarCRM. Can anybody provide an answer (can be theoretically based on technological approach or better - from experience).

Thanks

[stevec]

There are numbers and associated hardware specs in the faq:

http://www.sugarcrm.com/crm/products...tml#technical2

[kpit]

Hello,

Scaling the severs are tricky and complicated. But more users can be added with the right combination of servers and network configuration including load balancing, database replication. The question comes down to how much you want to invest in hardware to support more than 250 on a single machine. The biggest problem is resource contention. The Database in order to operate efficiently need to have large amounts of ram to cache and process each database hit and it need to access disk drives for data that is not cached. The web server side needs memory and disk access to process each request. a few hundred php files are accessed and processed. All of these are usually on the same server on the same hard drive. These will bring down performance of the server as a whole.

Two things that can enhance the perfomance of a single server solution. First Max out the RAM on the system. The more RAM means more workspace without having to resort to using hard drives as temporary memory. The excess memory will be used to cache Harddrive access as well. Use a seperate harddrive for the database not just a seperate partition on the same harddrive. Having the database on a seperate harddrive will boost perfomance because you will eliminate the hard drive contention issues. One other optional change install a php accelerator such as Zend Optimizer or eAccelerator. The accelerators will cache in memory preprocessed PHP files and will not hit the disk unless the file is changed.

The best thing is to seperate the Database server from the webserver. Even multiple webservers can be tied to the same database server. The database servers can have replication providing multiple database servers to be accessed by even more webeservers. The system can scale to many thousands of users. At that point you will have to contend with bandwith issues.

In general this system can scale but it does take more advance systems adminstration skills to scale up and out on the system. Not to mention performance tunning the database to make more effecient use of memory.

A number is a hard thing to pin down with out usage information. Also are these simultanious users or total users. How many will be accessing the system at the same time.

[stevec]

The database servers can have replication providing multiple database servers to be accessed by even more webeservers. The system can scale to many thousands of users. At that point you will have to contend with bandwith issues.

Hi,

Is replication a valid solution? I though MySQL was limited to - realistically - one-way replication by log shipping. If you have any experience with near-synchronous two-way replication, please could you let us know your experiences?

Thanks

[stevec]

Just bumping this up - re the use of replication.