jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sxm <sx...@yahoo.com>
Subject Re: Performance of workspace copy
Date Wed, 07 Oct 2009 23:12:51 GMT

Guo,

   Avg time for copy is 250 msec per node which increases as total number of
nodes copied increases. We use workspace.copy(fromNodePath, toNodePath)  for
each node that need to be copied.

-Shailesh


Guo Du wrote:
> 
> On Wed, Oct 7, 2009 at 2:19 PM, sxm <sxm20@yahoo.com> wrote:
>>
>> thanks Stefan, great suggestions. Could you please comment on [2]
>>
>> 1. I tried
>> org.apache.jackrabbit.core.persistence.bundle.MySqlPersistenceManager, no
>> visible performance improvement.
>> 2. Binary data: We dont have any binary data. How can we be sure and
>> disable
>> the binary properties.
>> 3. We will try dataStore. Although, performance gains may not be
>> significant
>> as it appears to be using only two connections for the entire
>> transaction.
>> 4. Versionability is the basic requirement.
>> 5. Switching db also is not an option in short term, we certainly
>> consider
>> it for long term solution.
>>
>> -Shailesh
> 
> Copy a big number of node into memory without commit to db, it may
> have big performance impact.
> 
> If you copy 400 node taken 4 seconds, then copy 2000 node may taken
> little longer than 20 seconds. If it's much longer, you may review the
> way how it was copied.
> 
> -Guo
> 
> 

-- 
View this message in context: http://www.nabble.com/Performance-of-workspace-copy-tp25778413p25796027.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Mime
View raw message