Very Computer

by **Dave Romi** » Mon, 30 Jun 2003 11:20:29

Can anyone provide guidance for saving and restoring an XMLDOM object as a
binary blob? In a VB application, I need to repeatedly save and restore a
large, dynamic XML document. Currently, the CPU overhead of serialization
and de-serialization is KILLING performance.

I have done some tests and if I could persist the DOM as a binary blob, I
think the performance issues would be resolved. A pair of orthogonal
functions that translate between XMLDOM and byte array would be great.

Thanks for your assistance.
Dave

by **Oleg Tkachenk** » Mon, 30 Jun 2003 20:26:38

> Can anyone provide guidance for saving and restoring an XMLDOM object as a
> binary blob? In a VB application, I need to repeatedly save and restore a
> large, dynamic XML document. Currently, the CPU overhead of serialization
> and de-serialization is KILLING performance.

> I have done some tests and if I could persist the DOM as a binary blob, I
> think the performance issues would be resolved. A pair of orthogonal
> functions that translate between XMLDOM and byte array would be great.

I don't think it would help. Performance penalty of serializing and
deserializing of large object graph is unavoidable, you'd better avoid
save/restore of big DOM objects in your design, why do you need it, btw?
--
Oleg Tkachenko
http://www.tkachenko.com/blog
Multiconn Technologies, Israel

by **Dave Romi** » Tue, 01 Jul 2003 08:58:14

Oleg,
Thanks for responding, but serialization and deserialization in a
homogeneous environment provides nothing positive. It's a total waste of
resources regardless of how it's used. XML and related tools are very
powerful but their power is diluted from the senseless overhead of
serialization. Serialization is only applicable in a heterogeneous
environment and I heartily support it.
Dave

> > Can anyone provide guidance for saving and restoring an XMLDOM object as
a
> > binary blob? In a VB application, I need to repeatedly save and restore
a
> > large, dynamic XML document. Currently, the CPU overhead of
serialization
> > and de-serialization is KILLING performance.

> > I have done some tests and if I could persist the DOM as a binary blob,
I
> > think the performance issues would be resolved. A pair of orthogonal
> > functions that translate between XMLDOM and byte array would be great.
> I don't think it would help. Performance penalty of serializing and
> deserializing of large object graph is unavoidable, you'd better avoid
> save/restore of big DOM objects in your design, why do you need it, btw?
> --
> Oleg Tkachenko
> http://www.tkachenko.com/blog
> Multiconn Technologies, Israel

Very Computer

Save / restore XMLDOM avoiding serialization

Save / restore XMLDOM avoiding serialization

Save / restore XMLDOM avoiding serialization

Save / restore XMLDOM avoiding serialization