Alfresco Server configuration for production

[kpatel]

Hi All,

Currently, I am using alfresco community 5.0d version in production server.

We have allocated 16GB RAM to the hosted instance.

Currently, I am facing the issue of slowness. Also, out of box login API is taking 11 to 12 seconds to produce alf ticket.

Current subsystem properties.

### Solr indexing ###
index.subsystem.name=solr4
dir.keystore=${dir.root}/keystore
solr.host=localhost
solr.port.ssl=8443

The total size of the alf_data folder is 449GB. And here I am attaching the document which describes alf_data size. 

So can someone please suggest me any reason for this slowness?

[angelborroy · Accepted solution]

Probably this can help: /blogs/alfresco-premier-services/2017/05/16/troubleshooting-alfresco-performance-from-the-bottom-up 

[Hajar01234]

I made a project under Alfresco (setting up a digital library under alfresco), when I copy the alfresco file into my supervisor's machine does not work (my supervisor wants my project to work in his machine) can- will you help me please?

[cesarista]

Hi:

I see that you delete a lot in your instance (due the size of contentstore.deleted). This may require lots of resources for SOLR. Some basics recommendations included in Nathan's article :

- Increase JVM size and monitorize (at least via OOTB Support Tools)

- Reindex SOLR (if you delete a lot, your indices may be fat of deleted documents which occupy more space and perform worse when searching)

- Separate SOLR instance (use dedicated resources for your index and search server)

Regards.

--C.

[angelborroy]

Cesar Capillas‌

I guess that 90% of "contentstore.deleted" are DELETED nodes that are out of Database and SOLR.

If your assumption is true, and trashcan have been never been purged, then they have a huge node just under Archive root. And this can be also the cause of the low performance.