<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Slow database responses on requests for /alfresco/service/api/solr/metadata in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/slow-database-responses-on-requests-for-alfresco-service-api/m-p/281073#M234203</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We found out 2 reasons behind the slowness&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. The disk i/o on the data volume of the mysql database was much slower compared to other systems. We used sysbench random i/o test to validate that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. The folder in question above has a few million documents which seem to cause this query to get slower. Nor can we load the folder contents page from share to display anything (results in a timeout related error). We're planning to restructure this folder to have further sub folders so as to limit docs in each folder. There are indications that this would help, but does not sound right to be doing something like this. We may not really have this control for other similar cases that might come up in the future. I'm wondering if this would still be a limitation in newer versions of Alfresco say 5.x.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Feb 2016 06:51:21 GMT</pubDate>
    <dc:creator>amit_kapps</dc:creator>
    <dc:date>2016-02-16T06:51:21Z</dc:date>
    <item>
      <title>Slow database responses on requests for /alfresco/service/api/solr/metadata</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/slow-database-responses-on-requests-for-alfresco-service-api/m-p/281072#M234202</link>
      <description>Hello,We're experiencing some performance issues with Alfresco 4.0.e and a mysql 5.5 backend.Through a performance monitor I can see a lot of requests (not sure what is triggering these) getting hung up on DB with a response time of nearly 100-200s. In the extreme case its 3000secs.All these request</description>
      <pubDate>Wed, 20 Jan 2016 23:08:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/slow-database-responses-on-requests-for-alfresco-service-api/m-p/281072#M234202</guid>
      <dc:creator>amit_kapps</dc:creator>
      <dc:date>2016-01-20T23:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: Slow database responses on requests for /alfresco/service/api/solr/metadata</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/slow-database-responses-on-requests-for-alfresco-service-api/m-p/281073#M234203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We found out 2 reasons behind the slowness&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. The disk i/o on the data volume of the mysql database was much slower compared to other systems. We used sysbench random i/o test to validate that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. The folder in question above has a few million documents which seem to cause this query to get slower. Nor can we load the folder contents page from share to display anything (results in a timeout related error). We're planning to restructure this folder to have further sub folders so as to limit docs in each folder. There are indications that this would help, but does not sound right to be doing something like this. We may not really have this control for other similar cases that might come up in the future. I'm wondering if this would still be a limitation in newer versions of Alfresco say 5.x.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Feb 2016 06:51:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/slow-database-responses-on-requests-for-alfresco-service-api/m-p/281073#M234203</guid>
      <dc:creator>amit_kapps</dc:creator>
      <dc:date>2016-02-16T06:51:21Z</dc:date>
    </item>
  </channel>
</rss>

