About CRM performance dynamics
My boss asked me to do some research on the available CMS on the market because the cms we currently use is quite a mess.
As a .NET developer, it would be great for me to choose and implement Dynamics CRM because of its extensibility and perfect integration with the .NET environment and well-known tools.
All marketing sounds great, but I would like to know about common DISADVANTAGES QUESTIONS regarding this system.
Most importantly, how it works in a company with about 150 concurrent and very active users. I have heard that it is very slow compared to the competitors' system.
a source to share
The Dynamics CRM product group has published an excellent white paper with guidance and guidance for 500 concurrent users. You can learn a lot by studying this article. The link is here:
Microsoft Dynamics CRM 4.0 Hardware Offered for Deployment of Up to 500 Concurrent Users
a source to share
I cannot answer the question about the number of users / activity. I can refer you to the SDK article "Productivity Best Practices". I will speak for you who will write plugins (data access messages), custom pages that access CRM web services, and write SSRS reports. Several points that I can relate to:
-
Disable plugins. This is an attractive and important integration point in CRM. The fact that they list it as a performance issue is depressing. We've seen OutOfMemory exceptions related to plugin cache. We faced this issue by deploying to disk, not database. In the database, they reload the assembly and validate the signature every time the plugin is called. We believe this was eating up a large pile of objects. This is probably not a problem for your usual CRM implementation.
-
Limiting data received. Definitely. Avoid looking for / picklists / for bits you don't need when you can, as it causes an extra join. There won't be a huge deal with small entities. But if you want objects with a lot of attributes this might be. This is probably not a problem for a typical CRM setup. Good design in other cases should avoid this problem.
a source to share
I can't offer any advice on how it compares to its top competitors. I know that the main thing is that it is cheaper and is developing very actively.
I can say a little about performance, although it might help.
We have about 400 - 600 concurrent users using the system. The system is not particularly intensive on the web server. We have two for resliency - it would be a disaster if it went offline, but these servers are never taxed. They have a couple of virtual cores and 4 gigabytes.
Our database is 130 GB in size and is hosted on a 24-bit database server with 48 GB of RAM. It is grouped, but since SQL server cannot handle two active nodes, only one server is active.
The database server never gets the most out of it. However, there is one very important change that we needed to make, and I think MS advises all users of large CRM installations to do so now. By default, SQL Server has a blocking mode that blocks people from writing to the database while reading a row. In our system (and possibly many others) that cause huge problems.
We turned on another mode (I think it's called "snapshot isolation") or something like that. To be fair, although even if you had 200 concurrent users this won't be a problem until the more central tables like activitypointer and account get pretty big (in millions)
So, there is no doubt that CRM 2011 can handle many users if you have the right hardware and someone who understands SQL Server
NTN
S
a source to share