Performance problems loading xml documents with non-xml cont

Hi,

We have a mixed xml and html document that we want to store in Tamino. We have made a schema with some xml elements and then an element ?text? of type String to contain the html part. The html part is stored as CDATA.
It works fine, and we are able to store and retrieve the documents. The problem is performance. Trying to store a 300 Kb document takes around 4 minutes using Interactive Interface and much more using the Java API. Is it the wrong type we use for the ?text? element containing the html code? Or is this way not the possible way to store html code? Should we store it ad non-xml in stead (which we have tried and it seems to be very fast)?

Example of an xml document:

1

<![CDATA[




Rapport




content...






]]>



And the Schema:
<?xml version = "1.0" encoding = "UTF-8"?>
<xs:schema xmlns:xs = “http://www.w3.org/2001/XMLSchema” xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition”>
xs:annotation
xs:appinfo
<tsd:schemaInfo name = “content”>
<tsd:collection name = “reports”></tsd:collection>
<tsd:doctype name = “content”>
tsd:logical
tsd:contentclosed</tsd:content>
</tsd:logical>
</tsd:doctype>
tsd:adminInfo
tsd:versionTSD3</tsd:version>
tsd:created2002-12-03T11:38:14.743+01:00</tsd:created>
tsd:modified2002-12-03T11:38:14.743+01:00</tsd:modified>
</tsd:adminInfo>
</tsd:schemaInfo>
</xs:appinfo>
</xs:annotation>
<xs:element name = “content”>
xs:complexType
xs:sequence
<xs:element name = “reportId” type = “xs:int”></xs:element>
<xs:element name = “text”></xs:element>
</xs:sequence>
<xs:attribute name = “deleted” type = “xs:boolean” use = “required”>
xs:annotation
xs:appinfo
tsd:attributeInfo
tsd:physical
tsd:native
tsd:index
tsd:standard</tsd:standard>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:attributeInfo>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
<xs:attribute name = “id” type = “xs:int” use = “required”>
xs:annotation
xs:appinfo
tsd:attributeInfo
tsd:physical
tsd:native
tsd:index
tsd:standard</tsd:standard>
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:attributeInfo>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:schema>

Many regards from

Ole Engele Nielsen

InterResearch A/S - Trekronergade 126 F - 2500 Valby
Phone: +45 70 27 28 72 - Mobile: +45 20 10 21 74 - Fax: +45 36 14 80 20
E-mail: oen@interresearch.dk - Homepage: http://www.interresearch.net/

Hi Ole,
I just replayed your scenario and loaded the document you provided two times into Tamino 4.1.0.544 (close to Washington) with the TII and the Xplorer. Both times it was very fast. Even replacing an old entry happened very fast. Which Tamino are you using and on what kind of machine?
Regards,
Gerald


Gerald Ristow
Tamino R&D

Hi Ole,
I think your application can be more fast/scalable/maintenanceable if your schema will use xs:any (with skip processing attribute) or “open feature” (just by Tamino) in place of CDATA section. Of course, it is depending by what you want to do ;O)

bye


Michelangelo Serpico
Software AG

+39 02950011.1
+39 3488205068
michelangelo.serpico@softwareag.com