On Tue, Jul 28, 2009 at 6:07 PM, Ajai wrote:
> I used profiler to look into this issue, It seems PDFbox is taking a lot of
> time.
> Also i had set "indexMergerPoolSize" parameter to 50, "extractorPoolSize"
> parameter to 50.
>
> Can you help me to resolve this problem.
Disable the search index to
nputStream(file));
>>>> Calendar lastModified = Calendar.getInstance();
>>>> lastModified.setTimeInMillis(file.lastModified());
>>>> resNode.setProperty("jcr:lastModified", lastModified);
>>>> // finally
>>>> session.save()
can be done.
>>>
>>
>>
>> Your code doesn't show details of the loop.
>>
>>
>> WRONG
>> ==
>> loop{ // 375000 times
>> addNode(...)
>> }
>> session.save();
>> ==
>>
>>
>>
>> CORRECT
>> ==
>> loop{ // 375000 times
>> addNode(...)
>> session.save();
>> }
>> ==
>> You may also add multiple documents before call session.save() to take
>> advantage of batch process more efficiently. But not after add all
>> 375000 documents.
>>
>> --Guo
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Performance-of-Jackrabbit-tp24619853p24681862.html
> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>
>
On Mon, Jul 27, 2009 at 3:36 PM, Ajai wrote:
> But i do have text extractors and indexes turned on.
Sorry, I didn't know how the index affect your result.
Good luck!
-Guo
k out the document? Are you mean add and save
>> documents to repository?
>>
>> I am not sure how you save the documents. The save do the actual
>> persistent to db, so you should avoid keep a big change list in your
>> mem before call save.
>>
>> --Guo
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Performance-of-Jackrabbit-tp24619853p24681170.html
> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>
>
>>
>> Please suggest if any changes can be done.
>>
>
>
> Your code doesn't show details of the loop.
>
>
> WRONG
> ==
> loop{ // 375000 times
> addNode(...)
> }
> session.save();
> ==
>
>
>
> CORRECT
>
On Mon, Jul 27, 2009 at 2:56 PM, Ajai wrote:
>
> Hi Guo,
>
> Yes, i am adding a document to the repository.
> Is there multiple ways to do a save?
>
> I am doing it the following way,
>
> fileNode = matterNode.addNode(fileName, "nt:file");
> fileNode.addMixin("mix:versionable");
> fileNode.addMixin
VM heap size
>> also
>> is around 1.5GB.
>
> When did you check out the document? Are you mean add and save
> documents to repository?
>
> I am not sure how you save the documents. The save do the actual
> persistent to db, so you should avoid keep a big change list in
> I tried using the Derby database to upload 375000 Documents.
>
> When i tried to add a document to this setup. It took more than 30 mins to
> do a checkin,
> The system CPU utilization was around 90% to 100% and the JVM heap size also
> is around 1.5GB.
When did you check out the document? Are y
ith 15 docs each, takes ~
>>>> 20
>>>> mins for a empty repository,
>>>>
>>>> After uploading 25000 folders, when trying to add same 500 Folders with
>>>> 15
>>>> docs each, it takes ~ 5 hrs.
>>>>
>>>
On Thu, Jul 23, 2009 at 2:05 PM, Bart van der
Schans wrote:
> On Thu, Jul 23, 2009 at 1:50 PM, Guo Du wrote:
>> On Thu, Jul 23, 2009 at 12:37 PM, Bart van der
>> Schans wrote:
>>> Iirc there's a similar problem with multi value properties when you
>>> add a lot of values.
>>>
>>> Is there any room
> all figures are way too high. please provide more information on your
>> setup/configuration and environment. if possible, please also provide
>> some code of your tests.
>>
>> cheers
>> stefan
>>
>>> So is there a way to improve the performance
On Thu, Jul 23, 2009 at 1:50 PM, Guo Du wrote:
> On Thu, Jul 23, 2009 at 12:37 PM, Bart van der
> Schans wrote:
>> Iirc there's a similar problem with multi value properties when you
>> add a lot of values.
>>
>> Is there any room left in the current implementation to improve the
>> performance of
On Thu, Jul 23, 2009 at 12:37 PM, Bart van der
Schans wrote:
> Iirc there's a similar problem with multi value properties when you
> add a lot of values.
>
> Is there any room left in the current implementation to improve the
> performance of those two use cases? Or did somebody already look at it
On Thu, Jul 23, 2009 at 1:00 PM, Alexander Klimetschek wrote:
> On Thu, Jul 23, 2009 at 9:31 AM, Ajai wrote:
>> http://www.nabble.com/file/p24620741/ThreadFeeder.java ThreadFeeder.java
>> http://www.nabble.com/file/p24620741/repository.xml repository.xml
>> http://www.nabble.com/file/p24620741/inde
On Thu, Jul 23, 2009 at 12:27 PM, Guo Du wrote:
> The size of uploaded file may affect the result significantly.
>
> I read some email that some one said the uploaded file are stored
> based on the hash value. This means your 15 unique files only
> stored/indexed once, it may not the real world ca
On Thu, Jul 23, 2009 at 9:31 AM, Ajai wrote:
> http://www.nabble.com/file/p24620741/ThreadFeeder.java ThreadFeeder.java
> http://www.nabble.com/file/p24620741/repository.xml repository.xml
> http://www.nabble.com/file/p24620741/indexingconfiguration.xml
> indexingconfiguration.xml
>
> Kindly let me
with
>>> 15
>>> docs each, it takes ~ 5 hrs.
>>>
>>
>> all figures are way too high. please provide more information on your
>> setup/configuration and environment. if possible, please also provide
>> some code of your tests.
>>
>> cheers
ossible, please also provide
> some code of your tests.
>
> cheers
> stefan
>
>> So is there a way to improve the performance of above mentioned functions
>> ?.
>>
>> Also kindly suggest an alternate solution to perform bulk upload?
>>
>> Thanks
&
functions ?.
>
> Also kindly suggest an alternate solution to perform bulk upload?
>
> Thanks
> Ajai G
>
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/Performance-of-Jackrabbit-tp24619853p24619853.html
> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>
>
tions ?.
Also kindly suggest an alternate solution to perform bulk upload?
Thanks
Ajai G
--
View this message in context:
http://www.nabble.com/Performance-of-Jackrabbit-tp24619853p24619853.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
21 matches
Mail list logo