cancel
Showing results for 
Search instead for 
Did you mean: 

Alfresco Performance Issue

vishky
Champ in-the-making
Champ in-the-making
We are using alfresco community 4.0 version server. I m geting performance issue on our Alfresco server.

Initially we are uploading 1000 files within  1 hour but now only 100 files are able to upload the alfresco server through our java batches.

we are using alfresco web service's for uploading and downloading the files.

we are using following environment:

1 Alfresco 3.4 community version

2 DB postgres 9.2

3 Alfresco app server Details
   

    OS                  App server      RAM             CPU             
   Linux 6.6 64bit       Tomcat 6       12 GB            4

JVM setting    -server -Xss1M -Xms3G -Xmx6G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewSize=2G -XX:MaxPermSize=1G -XX:CMSInitiatingOccupancyFraction=80

4 Postgres Server Details:

   OS                 RAM            CPU
Linux 6.6 64bit       8 GB            4


Data details on the alfresco app server.

folder                      size

/CMS_data/contentstore       1.5 Tera bytes

/CMS_Index/lucene-indexes    39 GB



Details of alfresco.global.properties

#
dir.root=/CMS_Data

# The location for lucene index files
dir.indexes=/CMSIndex/lucene-indexes

# The location for index backups
dir.indexes.backup=/CMSIndex/backup-lucene-indexes
#


#  database connection properties
#
#db.username=alfresco
#db.password=alfresco
### database connection properties ###
db.name=postgres
db.username=usrname
db.password=pasword
db.host=192.xxx.xxx.xxx
db.port=xxx
db.driver=org.postgresql.Driver
db.url=jdbcSmiley Tongueostgresql://${db.host}:${db.port}/${db.name}

alfresco.cluster.name=CMSCluster


4 REPLIES 4

niketapatel
Star Contributor
Star Contributor
Initally it was working OK, might be due to less concurrent/casual users, not sure about it. But First I would suggest to tune your JVM as per - https://wiki.alfresco.com/wiki/JVM_Tuning

Next, You should consider below some points to make your upload faster.
1)If you have system usage enable then you should turn off if you are really not using it. -system.usages.enabled=false
2)You should disable in Transaction lucene Indexing
3)You should turn off modification timestamp propogation. system.enableTimestampPropagation=false

You need to consider alfresco features which you are really not using those all should be disable like auditing, content preview [set some preview limit], entire content indexing etc…

Hope this helps!

vishky
Champ in-the-making
Champ in-the-making
Thanks Niketa

According to JVM_tuning post our server configuration is ok . WE set our JVM "-server -Xss1M -Xms3G -Xmx6G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewSize=2G -XX:MaxPermSize=1G -XX:CMSInitiatingOccupancyFraction=80"

I have one doubt we set XX:MaxPermSize=1G   our total RAM 12 GB inthis server. its may be the reason of performance issue. Can u confirm what should perfect value for this.

For second Consideration

Please tell me in which file we get all these option for disable . Its very helpful for me

1)system.usages.enabled=false
2)You should disable in Transaction lucene Indexing
3)You should turn off modification timestamp propogation. system.enableTimestampPropagation=false

You need to consider alfresco features which you are really not using those all should be disable like auditing, content preview [set some preview limit], entire content indexing etc…
ID 190881
thanks in Advance
Vishal

niketapatel
Star Contributor
Star Contributor
Hi Vishal, You can get almost all these OOB properties in repository.properties
and content transform limit you can check here - http://wiki.alfresco.com/wiki/Content_Transformation_Limits

rjohnson
Star Contributor
Star Contributor
We had a suddenly performance problem which ended up being memory related and cause the system to be almost continuously doing garbage collection.

I suggest you ajust your JVM launch settings to give you full details of GC activity and see how often GC is running. If you have very high frequency full GC, this is quite possibly the issue.