You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Cordenier Christophe <Ch...@atosorigin.com> on 2009/05/04 10:12:54 UTC
Tapestry 5.0.18 : Asset Localization.
Hello,
I'm sorry to insist on this point, but we have made more tests in a real production environment with more complex scenarii. When we use a decorator that hold references on assets using a key made of Path/Locale and we have a gain of 50% in CPU usage. It appears that the file existence check is really time consuming even when the resource is on the local filesystem.
I think this is quite interesting, but maybe I'm wrong.
Can anybody tell me if it has sense or not to implement such a behaviour ?
Thanks in advance,
Christophe.
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
RE: Tapestry 5.0.18 : Asset Localization.
Posted by Cordenier Christophe <Ch...@atosorigin.com>.
Here is a copy of what we can find with a 'kill -3' on heavy load :
at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:228)
at java.io.File.exists(File.java:702)
at org.apache.tapestry5.internal.services.ContextResource.toURL(ContextResource.java:69)
at org.apache.tapestry5.ioc.internal.util.AbstractResource.exists(AbstractResource.java:137)
at org.apache.tapestry5.ioc.internal.util.AbstractResource.forLocale(AbstractResource.java:104)
at org.apache.tapestry5.internal.services.AssetSourceImpl.findRelativeAsset(AssetSourceImpl.java:99)
at org.apache.tapestry5.internal.services.AssetSourceImpl.getAsset(AssetSourceImpl.java:93)
at $AssetSource_120aa1be8af.getAsset($AssetSource_120aa1be8af.java)
In earlier version of JDK (1.4), this method "getBooleanAttributes0" is associated to several hang problems in different java forum (as this one : http://forums.sun.com/thread.jspa?threadID=5228494)
The CPU utilization is maybe due to the corresponding fix, but I didn't found something relevant about this on the web.
-----Message d'origine-----
De : Howard Lewis Ship [mailto:hlship@gmail.com]
Envoyé : lundi 4 mai 2009 19:11
À : Tapestry development
Objet : Re: Tapestry 5.0.18 : Asset Localization.
Sounds reasonable ... when I was profiling Tapestry (part of the
performance improvements effort), I didn't see a lot of CPU
utilization related to assets, but the application I was using didn't
use many so it could not have shown up.
On Mon, May 4, 2009 at 1:12 AM, Cordenier Christophe
<Ch...@atosorigin.com> wrote:
> Hello,
>
> I'm sorry to insist on this point, but we have made more tests in a real production environment with more complex scenarii. When we use a decorator that hold references on assets using a key made of Path/Locale and we have a gain of 50% in CPU usage. It appears that the file existence check is really time consuming even when the resource is on the local filesystem.
>
> I think this is quite interesting, but maybe I'm wrong.
> Can anybody tell me if it has sense or not to implement such a behaviour ?
>
> Thanks in advance,
> Christophe.
>
> ________________________________
>
> Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
Director of Open Source Technology at Formos
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Tapestry 5.0.18 : Asset Localization.
Posted by Howard Lewis Ship <hl...@gmail.com>.
Sounds reasonable ... when I was profiling Tapestry (part of the
performance improvements effort), I didn't see a lot of CPU
utilization related to assets, but the application I was using didn't
use many so it could not have shown up.
On Mon, May 4, 2009 at 1:12 AM, Cordenier Christophe
<Ch...@atosorigin.com> wrote:
> Hello,
>
> I'm sorry to insist on this point, but we have made more tests in a real production environment with more complex scenarii. When we use a decorator that hold references on assets using a key made of Path/Locale and we have a gain of 50% in CPU usage. It appears that the file existence check is really time consuming even when the resource is on the local filesystem.
>
> I think this is quite interesting, but maybe I'm wrong.
> Can anybody tell me if it has sense or not to implement such a behaviour ?
>
> Thanks in advance,
> Christophe.
>
> ________________________________
>
> Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
Director of Open Source Technology at Formos
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org