You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by "Lefrancois, Carl" <Ca...@axa-canada.com> on 2008/09/11 20:35:44 UTC
RE : Memory footprint
Saad, I think you will find that Axis2/C gives you the best control
over your memory footprint since you can adapt the code to your needs.
I may be wrong here but I think the design philosophy of Axis2/C is
concentrated on runtime speed and so has nothing like memory
optimisation taken into consideration. I give as an example of this
thinking the frequent occurrence of variables like this:
axis2_char_t text_value_1[64];
defined in code generated from WSDLs (sometimes these variables aren't
even referenced in the generated code!).
-----Message d'origine-----
De : Saad Nader [mailto:snader@gamespy.com]
Envoyé : jeudi, septembre 11, 2008 12:46
À : Apache AXIS C User List
Objet : RE: Memory footprint
No more than 200-300 KB footprint for the client runtime just to do SOAP
operations. I like the generated soap serialization/deserialization
from WSDLs but I cannot afford to use 2-4MB for this because the system
only has 4 MBs.
Thanks,
------------------------
Saad Nader
Middleware Engineer
Powered By Gamespy
www.poweredbygamespy.com
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa@wso2.com]
Sent: Thursday, September 11, 2008 6:33 AM
To: Apache AXIS C User List
Subject: Re: Memory footprint
What are the memory footprint expectations you have?
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
Saad Nader wrote:
>
> Hello All,
>
> We're working on some middleware that will run on embedded devices. We
> need to consider memory footprint before using the Axis2 system. What
> is the typical memory footprint that a simple echo app uses for each
> module? We will be using the http sender and receiver.
>
> Thanks,
>
> ------------------------
>
> Saad Nader
>
> Middleware Engineer
>
> Powered By Gamespy
>
> www.poweredbygamespy.com
>
>
------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.169 / Virus Database: 270.6.19/1664 - Release Date:
9/10/2008 6:00 AM
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
_____
"Ce message est confidentiel, à l'usage exclusif du destinataire
ci-dessus et son contenu ne représente en aucun cas un engagement de la
part de AXA, sauf en cas de stipulation expresse et par écrit de la part
de AXA. Toute publication, utilisation ou diffusion, même partielle,
doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
message, merci d'en avertir immédiatement l'expéditeur."
"This e-mail message is confidential, for the exclusive use of the
addressee and its contents shall not constitute a commitment by AXA,
except as otherwise specifically provided in writing by AXA. Any
unauthorized disclosure, use or dissemination, either whole or partial,
is prohibited. If you are not the intended recipient of the message,
please notify the sender immediately."
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: RE : Memory footprint
Posted by Samisa Abeysinghe <sa...@wso2.com>.
And I think you can cut down the unwanted parts form the feature list to
get this amount of footprint. As an example, if your usage is limited to
clients, then you can drop the service histing capabilities.
Samisa...
Lefrancois, Carl wrote:
> Saad, I think you will find that Axis2/C gives you the best control
> over your memory footprint since you can adapt the code to your needs.
>
> I may be wrong here but I think the design philosophy of Axis2/C is
> concentrated on runtime speed and so has nothing like memory
> optimisation taken into consideration. I give as an example of this
> thinking the frequent occurrence of variables like this:
>
> axis2_char_t text_value_1[64];
>
> defined in code generated from WSDLs (sometimes these variables aren't
> even referenced in the generated code!).
>
>
>
> -----Message d'origine-----
> De : Saad Nader [mailto:snader@gamespy.com]
> Envoyé : jeudi, septembre 11, 2008 12:46
> À : Apache AXIS C User List
> Objet : RE: Memory footprint
>
>
> No more than 200-300 KB footprint for the client runtime just to do SOAP
> operations. I like the generated soap serialization/deserialization
> from WSDLs but I cannot afford to use 2-4MB for this because the system
> only has 4 MBs.
>
>
> Thanks,
> ------------------------
> Saad Nader
> Middleware Engineer
> Powered By Gamespy
> www.poweredbygamespy.com
>
>
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa@wso2.com]
> Sent: Thursday, September 11, 2008 6:33 AM
> To: Apache AXIS C User List
> Subject: Re: Memory footprint
>
> What are the memory footprint expectations you have?
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.169 / Virus Database: 270.6.20/1666 - Release Date: 9/11/2008 7:03 AM
>
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org