<?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: Alfresco and JCR performance requirements in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-and-jcr-performance-requirements/m-p/14141#M6068</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is something we will be looking at in detail early this year. High-load multi-user performance testing is high on the priority list.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would expect the performance of the JCR API to be a little lower than the pure Alfresco APIs as they are another layer mapped on-top of the Alfresco APIs. However, it shouldn't preclude you from using them as it won't be significant! Lucene performance has proven to be good so far, it is our aim to make sure you can search a repo of millions of documents in sensible response times.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Jan 2006 10:14:26 GMT</pubDate>
    <dc:creator>kevinr</dc:creator>
    <dc:date>2006-01-20T10:14:26Z</dc:date>
    <item>
      <title>Alfresco and JCR performance requirements</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-and-jcr-performance-requirements/m-p/14140#M6067</link>
      <description>Hello,I was wondering if there is a resource discussing hardware requirements for Alfresco.&amp;nbsp; What kind of performance can be expected from the JCR implementation?&amp;nbsp; What kind of hardware for how many simultaneous users?&amp;nbsp; Any help is greatly appreciated.Also, what about Lucene performance?&amp;nbsp; Most of ou</description>
      <pubDate>Tue, 20 Dec 2005 19:45:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-and-jcr-performance-requirements/m-p/14140#M6067</guid>
      <dc:creator>alexeyg</dc:creator>
      <dc:date>2005-12-20T19:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco and JCR performance requirements</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-and-jcr-performance-requirements/m-p/14141#M6068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is something we will be looking at in detail early this year. High-load multi-user performance testing is high on the priority list.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would expect the performance of the JCR API to be a little lower than the pure Alfresco APIs as they are another layer mapped on-top of the Alfresco APIs. However, it shouldn't preclude you from using them as it won't be significant! Lucene performance has proven to be good so far, it is our aim to make sure you can search a repo of millions of documents in sensible response times.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2006 10:14:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-and-jcr-performance-requirements/m-p/14141#M6068</guid>
      <dc:creator>kevinr</dc:creator>
      <dc:date>2006-01-20T10:14:26Z</dc:date>
    </item>
  </channel>
</rss>

