Well, I am not saying that my solution is the best and that other solutions
are bad. I am just saying that this solution looks very good to me.
But anyway it will be interesting to compare the two choices you say, and
probably others. I think I'll do it, later.
I do not know about the tools to 'simulate 1000+ users hitting the submit
button at the same time' so please give us more info about it.
Benjamin
-----Original Message-----
From: M. Simms [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 25, 2001 3:14 PM
To: [EMAIL PROTECTED]
Subject: Re: MVC, EJBs and Oracle
1) You of course "stress tested" with implementation with something like
Mercury's tools and such that would simulate 1000+ users hitting the submit
button at the same time ?
2) You of course compared this design to an MVC servlet/JSP implementation
using regular Beans and a pooled connection to the database ?
if not, then:
a) perform #1 for 100, 1000, 10000 simulated users
b) perform #2 for 100, 1000, 10000 simulated users
c) compare testing results of #1 to #2
THEN YOU CAN COME TO SOME VALID CONCLUSIONS.
BTW: You of course are not deploying EJB's for read-only queries, right ?
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nevarez, Benjamin
> Sent: Friday, May 25, 2001 4:36 PM
> To: [EMAIL PROTECTED]
> Subject: MVC, EJBs and Oracle
>
>
> Hello,
>
> I am writing an MVC application accessing an Oracle database. I am using a
> servlet as controller, JSP only for presentation (view) and EJBs for
> accessing data.
>
> I have seen that even with just a few records in the database the
> performance of the application is really good. So maybe it is a good idea
> using EJBs even for small applications. In this way you will not have to
> rewrite code if your application or data grow and it is already scalable.
>
> Somebody asked before about when to re-query the database. Of
> course we need
> to re-query the database every time and, as expected, the
> response times are
> very short after the first request. For example, the first time I
> do a query
> took 140 milliseconds, the next times it took 50, 40, 40, 40, etc.
>
> Of course you also get the benefits of MVC like cleanest separation of
> presentation, control and data.
>
> Please let me know if you have any comments,
>
> Benjamin
>
> ==================================================================
> =========
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set
> JSP-INTEREST DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
