You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/02/25 18:32:51 UTC

[jira] Created: (FELIX-500) Performance problems when using the OSGi classloaders in a certain way

Performance problems when using the OSGi classloaders in a certain way
----------------------------------------------------------------------

                 Key: FELIX-500
                 URL: https://issues.apache.org/jira/browse/FELIX-500
             Project: Felix
          Issue Type: Improvement
          Components: Framework
    Affects Versions: 1.0.3
            Reporter: Guillaume Nodet
            Priority: Critical


As discussed on the mailing list, there is a big performance problems when lots of CNFE are thrown from the framework.
The main reason is that the creation of the diagnosis message is very time consuming.
This patch aims to fix the problem by lazy creating the message only when needed (when the exception is actually displayed
or serialized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (FELIX-500) Performance problems when using the OSGi classloaders in a certain way

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall resolved FELIX-500.
-----------------------------------

    Resolution: Fixed

I applied the second patch and deployed new snapshots of framework and main. Please close this issue if everything is in order.

> Performance problems when using the OSGi classloaders in a certain way
> ----------------------------------------------------------------------
>
>                 Key: FELIX-500
>                 URL: https://issues.apache.org/jira/browse/FELIX-500
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.3
>            Reporter: Guillaume Nodet
>            Assignee: Richard S. Hall
>            Priority: Critical
>         Attachments: FELIX-500.patch, FELIX-500.patch
>
>
> As discussed on the mailing list, there is a big performance problems when lots of CNFE are thrown from the framework.
> The main reason is that the creation of the diagnosis message is very time consuming.
> This patch aims to fix the problem by lazy creating the message only when needed (when the exception is actually displayed
> or serialized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (FELIX-500) Performance problems when using the OSGi classloaders in a certain way

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall reassigned FELIX-500:
-------------------------------------

    Assignee: Richard S. Hall

> Performance problems when using the OSGi classloaders in a certain way
> ----------------------------------------------------------------------
>
>                 Key: FELIX-500
>                 URL: https://issues.apache.org/jira/browse/FELIX-500
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.3
>            Reporter: Guillaume Nodet
>            Assignee: Richard S. Hall
>            Priority: Critical
>         Attachments: FELIX-500.patch, FELIX-500.patch
>
>
> As discussed on the mailing list, there is a big performance problems when lots of CNFE are thrown from the framework.
> The main reason is that the creation of the diagnosis message is very time consuming.
> This patch aims to fix the problem by lazy creating the message only when needed (when the exception is actually displayed
> or serialized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (FELIX-500) Performance problems when using the OSGi classloaders in a certain way

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet closed FELIX-500.
---------------------------------


Works great, thx !

> Performance problems when using the OSGi classloaders in a certain way
> ----------------------------------------------------------------------
>
>                 Key: FELIX-500
>                 URL: https://issues.apache.org/jira/browse/FELIX-500
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.3
>            Reporter: Guillaume Nodet
>            Assignee: Richard S. Hall
>            Priority: Critical
>         Attachments: FELIX-500.patch, FELIX-500.patch
>
>
> As discussed on the mailing list, there is a big performance problems when lots of CNFE are thrown from the framework.
> The main reason is that the creation of the diagnosis message is very time consuming.
> This patch aims to fix the problem by lazy creating the message only when needed (when the exception is actually displayed
> or serialized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FELIX-500) Performance problems when using the OSGi classloaders in a certain way

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated FELIX-500:
----------------------------------

    Attachment: FELIX-500.patch

> Performance problems when using the OSGi classloaders in a certain way
> ----------------------------------------------------------------------
>
>                 Key: FELIX-500
>                 URL: https://issues.apache.org/jira/browse/FELIX-500
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.3
>            Reporter: Guillaume Nodet
>            Priority: Critical
>         Attachments: FELIX-500.patch, FELIX-500.patch
>
>
> As discussed on the mailing list, there is a big performance problems when lots of CNFE are thrown from the framework.
> The main reason is that the creation of the diagnosis message is very time consuming.
> This patch aims to fix the problem by lazy creating the message only when needed (when the exception is actually displayed
> or serialized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FELIX-500) Performance problems when using the OSGi classloaders in a certain way

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated FELIX-500:
----------------------------------

    Attachment: FELIX-500.patch

Original idea from Stuart.

> Performance problems when using the OSGi classloaders in a certain way
> ----------------------------------------------------------------------
>
>                 Key: FELIX-500
>                 URL: https://issues.apache.org/jira/browse/FELIX-500
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.3
>            Reporter: Guillaume Nodet
>            Priority: Critical
>         Attachments: FELIX-500.patch
>
>
> As discussed on the mailing list, there is a big performance problems when lots of CNFE are thrown from the framework.
> The main reason is that the creation of the diagnosis message is very time consuming.
> This patch aims to fix the problem by lazy creating the message only when needed (when the exception is actually displayed
> or serialized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.