geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan <xhh...@gmail.com>
Subject Re: [DISCUSS] Reduce 2.2 server footprint by making some current plugins optional
Date Tue, 16 Sep 2008 15:35:08 GMT
I guess that Dojo should be kept, for I remember there is a thread about
using Dojo to doing the input validation in the admin console.

2008/9/16 Donald Woods <dwoods@apache.org>

> Did a quick experiment with removing some "optional" items from the Tomcat
> assembly (results are using Java 5 on a 2.4GHz Core 2 Duo system running
> openSUSE 11.0.)
>
> The current geronimo-tomcat6-javaee5 tar.gz assembly for trunk I built last
> night is 87.1 MB, takes 23.5 secs to start and uses 170MB RAM.
>
> If we removed the following from the assembly and made them optional
> plugins that the user can install if they want these features -
>  - MConsole
>  - Dojo
>  - Debug Views
>  - Plan Creator
>  - CXF
>
> Then the tar.gz drops to 79.5 MB, takes 19 secs to start and uses 155MB
> RAM.  About 2.8 secs was for the Monitoring Console and agent support, with
> another 0.5 secs being the Plan Creator and Debug Views.
>
>
> -Donald
>
>
>
> Donald Woods wrote:
>
>> Someone mentioned on another thread(s) awhile back that they would like to
>> see us reduce the server footprint and startup time for 2.2.
>>
>> One way to do this (mainly for footprint) would be to start moving some of
>> the plugins that are not required for a JEE5 runtime out of the server
>> assemblies we create and made available as optional user installable plugins
>> (from the normal maven repos.)
>>
>> I'm proposing that we remove the following from the default server
>> assemblies as a start:
>>  - Debug Views
>>  - Monitoring
>>  - Plan Creator
>>
>> We can either update the Welcome Portlet to mention these are available
>> from the Plugin repo or create a "placeholder" portlet for each that
>> describes what the optional plugin provides along with a link to install the
>> full version.  Also, the testsuite would be updated to install the required
>> plugin before any tests are executed against it.
>>
>> Thoughts?
>>
>>
>> -Donald
>>
>>
>>


-- 
Ivan

Mime
View raw message