Hi,

I was observing the start-up time in the M3 pack with gradual load. At the
addition of every 10 web apps I used to restart the server and check the
start-up time. The trend was as the table below. It was a flat trend within
11-13 secs.

After 100 webapp load, I restarted the machine and restarted the server.
This time the start-up delay was 22 secs. Any clue why this increase could
be?




# of webapps Server startup time (sec)  Default server 2 11  With load
10 11  With
load 20 12  With load 30 12  With load 40 12  With load 50 12  With load 60
12  With load 70 13  With load 80 13  With load 90 12  With load 100 13  With
load after host is restarted 100 22


[image: Inline image 1]



Thanks,
Yumani






On Tue, Feb 28, 2012 at 5:31 PM, Nuwan Bandara <[email protected]> wrote:

> Hi All,
>
> Internally we have hosted the M3 pack at [1] welcome your feedback, and
> please report the issues at [2]
>
> [1] http://jaggery.private.wso2.com:9767/docs
> [2] https://wso2.org/jira/browse/JAGGERY
>
> ---------- Forwarded message ----------
> From: Nuwan Bandara <[email protected]>
> Date: Tue, Feb 28, 2012 at 5:29 PM
> Subject: [ANN] Jaggery Milestone-3 Released
> To: carbon-dev <[email protected]>
>
>
> *Introducing Jaggery*
>
> Jaggery is a framework to write webapps and HTTP-focused web services for
> all aspects of the application: front-end, communication, Server-side logic
> and persistence in pure Javascript. One of the intents of this framework is
> to reduce the gap between writing web apps and web services.
>
> This Framework uses Mozilla Rhino to process Javascript at the server and
> also contains a powerful caching layer with the support of Rhino compiled
> scripts; so its as fast as the JVM. As few key features, Jaggery has native
> JSON support and also E4X support for XML manipulation.
>
> M3 can be downloaded at http://dist.wso2.org/products/jaggery/dl/jaggery
> -1.0.0-SNAPSHOT_M3.zip
>
> *Say Hello to Jaggery*
>
> <html>
>
> <body>
>
>  <h1>
>
> <%
>
>    var name = 'Jaggery';
>
>    print("Hello " + name);
>
> %>
>
> </h1>
>
> </body>
>
> </html>
>
> *Setting up Jaggery*
>
>    1. Extract jaggery-1.0.0-SNAPSHOT_M3.zip
>    2. This will generate a bin directory with execution scripts.
>    3. Run sh bin/wso2server.sh (bin/wso2server.bat) command to start the
>    server.
>    4. Upon successful startup, {http://localhost:9763/docs} should take
>    you to the documentation Jaggery App.
>
> *Key Features*
>
>
>    - Compose server side scripts purely in javascript (.jss)
>    - Script caching support
>    - Script include support
>    - Module include support
>    - Command line tool for easy development
>    - Try-it tool for web based script validation
>    - Includes support for,
>       - HTTP request/response and session
>       - JSON send/receive
>       - Server side XMLHttpRequest
>       - URIMatcher
>       - Web Service invocation
>       - File I/O
>       - Email
>       - XSLT
>       - Atom
>       - Read/write feed
>       - Relational database
>       - WSO2 Registry/Repository
>
> For more information and samples you can refer to Jaggery docs at (
> http://{yourip}:9763/docs/documentation.jss<http://localhost:9763/docs/documentation.jss>
> ) which are shipped with the distribution
>
>
> Thanks,
> *Jaggery Development Team*
>
> <http://www.nuwanbando.com/>
>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://nuwan.bandara.co
> *
> <http://www.nuwanbando.com/>
>



-- 
Yumani Ranaweera
Associate Technical Lead - QA
WSO2, Inc. - http://wso2.org

Email : [email protected]
Cell    : +94 077 7795242
Blog   : http://yumani.blogspot.com/

<<Screenshot-13.png>>

_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to