You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Scott Cantor (JIRA)" <ji...@apache.org> on 2017/12/27 15:05:00 UTC

[jira] [Updated] (SANTUARIO-267) high memory and processor time cost while signing big files

     [ https://issues.apache.org/jira/browse/SANTUARIO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor updated SANTUARIO-267:
-----------------------------------
    Affects Version/s: C++ 2.0.0
                       C++ 1.7.3

> high memory and processor time cost while signing big files
> -----------------------------------------------------------
>
>                 Key: SANTUARIO-267
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-267
>             Project: Santuario
>          Issue Type: Task
>      Security Level: Public(Public issues, viewable by everyone) 
>          Components: C++
>    Affects Versions: C++ 1.5.1, C++ 1.6.0, C++ 1.6.1, C++ 1.7.0, C++ 1.7.1, C++ 1.7.2, C++ 1.7.3, C++ 2.0.0
>         Environment: OS: Windows 7 x64 
> Build: MS Visual Studio 2010 (x86 and x64)
> Xerces 3.1.1
>            Reporter: Maxim Makeev
>            Assignee: Scott Cantor
>
> Test file (36MB) is XML document.
> Signing and verifying signature on this file takes 20 seconds, but .NET XML Sigature library makes it ten times faster..
> Bottleneck is canonicalisation. TXFMC14n::readBytes gets too much processor's time while operation. Any canonicalization type works this way.
> Application allocates ~360MB (x86) and ~700MB(x64) while signing. Half of this memory allocates while parsing XML and half while canonisation...
> Its to much, because we need to work with big documents. Is it possible to optimize this operations? 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)