You have given us only one part of the important information required, you have that many users but what is your hardware like?
Please have a look at this post it may be of some help
We have implemented Alfresco for large storage (millions of documents; with around 10 TB of data and meta-data) in Production environment. However we had a clustered deployment to manage the load and to give us good performance.
There might be various reasons for slow performance which are both Alfresco related and non-Alfresco related. You need to locate the actual problem.
Non-Alfresco related: - Network issues - Database connectivity issues - File System Access issues - Slower LDAP or Active Directory (if used) - Server (CPU) Power etc… - Number of people using Alfresco at a specific point of time (large number of concurrent users)
Alfresco Related:
- File operations (add/edit/delete) in a space which has LARGE number of files takes more time.
- Having versionable aspect on new nodes has a huge negative impact on performance. Some noticed more than 50% improvement in performance by not applying versioning.
- File operations in a space which has business rules (run in foreground not in background) takes up good amount of time. For example the rules such as transforming content from Word to PDF, executing custom Javascript etc.
- Unbalanced deployment of Alfresco (need to check the topology of your production deployment)
- Unsupported Stack of Alfresco (Please check Alfresco website for the stack supported)
- Community version or Older version which has known performance related bugs (Use the latest Enterprise tested version)
- Too much of logging the details (see if you have DEBUG option enabled in Production environment)
- Enabled Audit Trail (By default this is OFF), which does lots of extra activities for each operation
- the list goes on … depending upon the way you implemented Alfresco
Review your production deployment for such situations.
Alfresco is deployed for large production environments (for 80 million page views / month, for 10 TB of data etc..), hence it is a proven stable platform for enterprise roll-outs. May be consider getting a supported (Enterprise) version which saves lots of your time.
Also if you have made any changes to lucene indexes setting i would sudgest looking back at it and setting it back to the default setting of The index.recovery.mode=VALIDATE in repository properties
