You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2008/02/05 12:00:14 UTC
[jira] Updated: (JCR-1300) spi2dav Improve performance for large
binary properties
[ https://issues.apache.org/jira/browse/JCR-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-1300:
------------------------
Component/s: (was: jackrabbit-spi)
contrib
(wrong component)
> spi2dav Improve performance for large binary properties
> -------------------------------------------------------
>
> Key: JCR-1300
> URL: https://issues.apache.org/jira/browse/JCR-1300
> Project: Jackrabbit
> Issue Type: Improvement
> Components: contrib, jackrabbit-jcr-server
> Reporter: Jozef Wagner
>
> Sending large binary properties over spi2dav is slow and requires a lot of heap space in both client and server.
> One problematic part is base64 conversion of the property value.
> On the contrary, using 'normal' webdav interface (/repository/default/ instead of /server) for uploading a file (through traditional webdav client) it is pretty fast and don't have such impact on heap space.
> Some suggestions from the previous discussion:
> - avoid temporary copies of the data, and persist large objects as early as possible.
> - transfer large objects in blocks from the Jackrabbit SPI client to the server (and back).
> - make usage of the global data store (JCR-926).
> - straight forward PUT for single-valued properties
> Link to discussion: http://www.mail-archive.com/dev@jackrabbit.apache.org/msg09481.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.