geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Genender <jgenen...@apache.org>
Subject Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release
Date Wed, 03 Oct 2007 14:36:19 GMT


Christopher Blythe wrote:
> Jeff... I agree with you on both counts. Perhaps I should present this
> from another vantage point. If you were an application developer, would
> you use web services in the manner they are currently used in DayTrader?
> Or would you try to adhere to most documented best practices and steer
> clear of very chatty (fine-grained) web services calls. If we would like
> to keep web services in DayTrader, I think they should be re-vamped to
> re-align with a scenario/pattern that is better suited for web services
> and reflect how they are predominantly used in the industry.
> 

Yep...you are going exactly where I was ;-)

If DT is not using WS the way it should be, then absolutely it should be
redone and developed in a best practice manner.

Jeff



> On 10/3/07, *Jeff Genender* <jgenender@apache.org
> <mailto:jgenender@apache.org>> wrote:
> 
> 
> 
>     Christopher Blythe wrote:
>     > Actually, I'm suggesting we pull the web services out of DayTrader all
>     > together and write another web services sample app. If DayTrader is
>     > truly meant to be a "performance benchmark", why would you leave
>     > something in there that is in clear violation of performance best
>     > practices. Doesn't exactly send the right message if you ask me.
>     >
> 
>     That really depends what you are trying measure.  Are you trying to
>     measure raw-throughput (ping servlet, etc), or are you trying to measure
>     how a JavaEE5 application using standard components is going to perform
>     (more realistic)?
> 
>     IMHO, I think Daytrader is a neat application that lets you kind of
>     configure what you want to test and how you want to test it.  Its
>     interesting because I haven't seen anything else out there that does
>     this...it really is a good way to measure most components of a
>     standardized stack.
> 
>     Jeff
> 
>     > On 10/2/07, *Matt Hogstrom* <matt@hogstrom.org
>     <mailto:matt@hogstrom.org>
>     > <mailto:matt@hogstrom.org <mailto:matt@hogstrom.org>>> wrote:
>     >
>     >
>     >     On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:
>     >
>     >     > Matt...
>     >     >
>     >     >
>     >     > In summary, I guess I really just wanted to say that I feel
>     the web
>     >     > services modes in DayTrader should be removed at least until
>     we can
>     >     > come up with something better. If the only reason to keep these
>     >     > around is to provide a "sample" and not a performance benchmark,
>     >     > lets come up with some other sample that demonstrates web
>     services.
>     >     >
>     >
>     >     You make a good point about the WebServices.  I'd suggest that we
>     >     document the current limitations of comparing these WebServices in
>     >     performance benchmarks.  That should help to set everyone's
>     >     expectations about the relevant usefulness of the data.
>     >
>     >     For WebServices it sounds like your suggesting that we
>     deprecate web
>     >     services for performance work rather than for functional purposes
>     >     like was done for the MDB primitives.  I'd be for adding the
>     warning
>     >     in a readme.
>     >
>     >
>     >
>     >
>     > --
>     > "I say never be complete, I say stop being perfect, I say let... lets
>     > evolve, let the chips fall where they may." - Tyler Durden
> 
> 
> 
> 
> -- 
> "I say never be complete, I say stop being perfect, I say let... lets
> evolve, let the chips fall where they may." - Tyler Durden

Mime
View raw message