[omniORB] anys and sequence<octet>
Renzo Tomaselli
renzo.tomaselli@tecnotp.it
Fri, 24 Dec 1999 10:43:08 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0034_01BF4DFB.AA90F560
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi OmniORB developers,
I noticed as OmniORB 2.8 deals with inserting/extracting sequences =
to/from anys.
Sequence elements are handled one-by-one in tcParser::copyFrom/to (in =
tcParser.cc) resulting in a terrific performance dropping in case of =
long sequences of octets, such as for graphical bitmaps. Each octet goes =
through a long number of operations to be copied in/out the any.
While tcParser::copyFrom(MemBufferedStream& mbuf) is optimized for this, =
resulting in a memcpy for the best case, =
tcParser::copyFrom(tcDescriptor& desc) is not, raising the above =
performance issue. The net result is that sending a octet sequence is =
fast, sending the same into an any is a double disaster.
This topic is somewhat related to a similar one in DynAnys (see a =
related posting sometime ago).
Thanks,
Renzo Tomaselli =20
-------------------------------------------------------------------------=
--
TecnoTP s.n.c. Special Information System Design
Maso Pelauchi I38050 Ronchi Valsugana, Trento TN ITALY
Tel. +39 0461 773164 Fax. +39 0461 771514
e-mail: renzo.tomaselli@tecnotp.it =20
-------------------------------------------------------------------------=
--
------=_NextPart_000_0034_01BF4DFB.AA90F560
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Hi OmniORB developers,</FONT></DIV>
<DIV><FONT size=3D2> I noticed as OmniORB 2.8 deals =
with=20
inserting/extracting sequences to/from anys.</FONT></DIV>
<DIV><FONT size=3D2>Sequence elements are handled one-by-one in=20
tcParser::copyFrom/to (in tcParser.cc) resulting in a terrific =
performance=20
dropping in case of long sequences of octets, such as for graphical =
bitmaps.=20
Each octet goes through a long number of operations to be copied in/out =
the=20
any.</FONT></DIV>
<DIV><FONT size=3D2>While tcParser::copyFrom(MemBufferedStream& =
mbuf) is=20
optimized for this, resulting in a memcpy for the best case,=20
tcParser::copyFrom(tcDescriptor& desc) is not, raising the above =
performance=20
issue. The net result is that sending a octet sequence is fast, sending =
the same=20
into an any is a double disaster.</FONT></DIV>
<DIV><FONT size=3D2>This topic is somewhat related to a similar one in =
DynAnys=20
(see a related posting sometime ago).</FONT></DIV>
<DIV><FONT size=3D2>Thanks,</FONT></DIV>
<DIV><FONT=20
size=3D2> &nbs=
p;  =
; =
=20
Renzo Tomaselli =20
<BR>---------------------------------------------------------------------=
------<BR>TecnoTP=20
s.n.c. Special Information System Design<BR>Maso Pelauchi I38050 Ronchi=20
Valsugana, Trento TN ITALY<BR>Tel. +39 0461=20
773164 Fax. +39 0461 771514<BR>e-mail: <A=20
href=3D"mailto:renzo.tomaselli@tecnotp.it">renzo.tomaselli@tecnotp.it</A>=
=20
<BR>---------------------------------------------------------------------=
------</FONT></DIV></BODY></HTML>
------=_NextPart_000_0034_01BF4DFB.AA90F560--