Sugar Architecture, HA guidelines

[JavaCK]

Hi,

I'm a new user to SugarCRM which Community Edition looks great (congratulations to the team by the way !), and I have a couple of questions regarding the deployment of SugarCRM :

I would like to know "what load" can sugarCRM support on "small hardware", say for instance :

• Red Hat Enterprise Linux AS 5 (OS: 32 bit; 2 Go RAM, 2 CPU) , MySQL Community Server Edition on a LAMP environment, All on the same box

• Red Hat Enterprise Linux AS 5 (OS: 32 bit; ; 4 Go RAM, 8 CPU) , 1 Load Balanced Apache Cluster (on 2 dedicated boxes) , MySQL Cluster with 2 nodes (2 dedicated boxes)

By "what load", I mean how many Sugar users / concurrent SQL connections are "supported" (before the system crashes) ?

From a low level point of view, does Sugar manages a connection pool with the DB ? is the connection opened during all the user ( logged to the sugar webapp) session or is it opened&closed after each HTTP request ?

Regards,

Steve

[andopes]

Hi,

I'm a new user to SugarCRM which Community Edition looks great (congratulations to the team by the way !), and I have a couple of questions regarding the deployment of SugarCRM :

I would like to know "what load" can sugarCRM support on "small hardware", say for instance :

• Red Hat Enterprise Linux AS 5 (OS: 32 bit; 2 Go RAM, 2 CPU) , MySQL Community Server Edition on a LAMP environment, All on the same box

• Red Hat Enterprise Linux AS 5 (OS: 32 bit; ; 4 Go RAM, 8 CPU) , 1 Load Balanced Apache Cluster (on 2 dedicated boxes) , MySQL Cluster with 2 nodes (2 dedicated boxes)

By "what load", I mean how many Sugar users / concurrent SQL connections are "supported" (before the system crashes) ?

From a low level point of view, does Sugar manages a connection pool with the DB ? is the connection opened during all the user ( logged to the sugar webapp) session or is it opened&closed after each HTTP request ?

Regards,

Steve

Hi Steve

It is difficult to say how many users a hardware supports until it gets crashed.
One of our server is smaller than these two and it is fine to at least 100 users.
A good strategy to make the architecture scalable is to configure one server to sugar itself (apache/php) and another one to the database. It improve the system performance.

I don't know about the connection pool, perhaps the guys from SugarCRM can answer this question.

Best regards and good luck!

[mcatling]

Depends what you are doing.... and I cant really comment on Linux.... but for what its worth.


On the system config detailed below I have a customer with 32 users but they only do about 20- 40 transactions a day each in a project management environment (Custom modules), not tele sales call centre or tele support help desk. They get about 2-3 second response times.

Pentium 4 - 2.8ghz
504mb ram available (after onboard graphics have had their share)
1 * 120gbPATA disk
Wampserver 2.0
Windows XP SP2
SugarCRM 5.0

In a call centre environment I have a different customer with 90 users and they do constant help desk (custom modules) and telesales (Asterix integration) work so push through many 1,000s of transactions per day. They get about a reliable1-2 second response time and system utilisation is low enough to allow growth of about 60%.

2 * Quad core Xenon 2.6ghz
4gb ram
2 * 3Ware sata raid controllers
2 sata disks 200gb in Raid 1 mirror for system and wampserver folder.
2 sata disks 200gb in Raid 1 mirror for documents folders
2 sata disks 120gb in Raid 1 mirror for Log files.
4 sata disks 200gb in a Raid 5 array for MySQL database
Windows server 2003
Wampserver 2.0
SugarCRM 5.0

One of the key things that I have found to performance is to follow the WIKI performance guides for setting up the system...

Also have a look at the Sugar cube offerings from the home page. They have some configs on there with a guideline to numbers of users you can support.

But most of all make sure that you have a good MySQL DB admin to keep the DB running smoothly.

For example if you create a saved search list view or create custom modules with complex list views that have a lot of sortable fields in the list view header. You need to make sure that you create an index for the sortable field in the database directly... easy with PHPMyAdmin but only if you know or remember to do it.

I have seen a number of system which have been brought to a crawl when two users of a custom module both try and sort list views with thousdands of records in them in different orders (Ascending/Decending)

Also i have seen a perfomance guide in the WIKI or Forum(sorry cant remember which) which shows the results of running 900 users on a Sun T5220 server. This gives some excellent guidelines on how to tune the database etc. SOrry I cant remeber where it is as I am mainly windows based. :-(

Best regards, Malcolm

[JavaCK]

Malcom, thanks for your reply

Sugar Team, could you please answer my last point :
"From a low level point of view, does Sugar manages a connection pool with the DB ? is the connection opened during all the user ( logged to the sugar webapp) session or is it opened&closed after each HTTP request ?"

This is important to understand how the connections are managed to size the DB ....

Thanks in advance,

Steve

[JavaCK]

Depends what you are doing.... and I cant really comment on Linux.... but for what its worth.



Also i have seen a perfomance guide in the WIKI or Forum(sorry cant remember which) which shows the results of running 900 users on a Sun T5220 server. This gives some excellent guidelines on how to tune the database etc. SOrry I cant remeber where it is as I am mainly windows based. :-(

Best regards, Malcolm

I think I have found the bench you were talking about on Sun Blogs

Cheers,

Steve