
READING
DEVELOPING
JIRA is Atlassian's J2EE bug tracking, issue tracking and project management package.
CONTACTING MIKE
I'm always happy to hear from you. Sometimes it helps to read "About" first.
Web: (via Radio)
ICQ:191468
AIM:mcannonbrookes
MSN:mcannonbrookes
Email:mike at atlassian.com
Cell:(612) 416 106090
Blog Chalk:
|
 |
rebelutionary Mike Cannon-Brookes on Java, J2EE, OSX, Open Source, Australia, Atlassian, Bug Tracking, JIRA and more...
 |
Friday, 6 September 2002 |
|
Anyone have any benchmarks or indications of whether JSP or Velocity is faster?
I would imagine that Velocity is more 'standard speed' across different containers. The problem we have at the moment is that our application runs well on Resin and Orion but unacceptably slowly on Tomcat and Jetty. Short of hacking at Jasper myself, I'm not sure what else to do.
Someone out there must have benchmarked them recently. The only link I can find is from an old tomcat-dev post about Tomcat 3.2.
|
5:32:55 PM |
|
Today I installed Clover and ran it over our JIRA bug tracking test suite. Wow!
It takes a little setting up but the results are well worthwhile. I thought our test suite was fairly comprehensive, but (I'm not sure if I should admit this!) it only covered 20.4% of the code!
After an hour or two of tweaking the suite, and we're up to 24.9% of the total - that's 26.1% of methods, 25.5% of statements and 22.7% of conditionals.
If you think keeping the JUnit test meter green is addictive, having an updated report of exactly how much code is covered is far more addictive. A measly 1% gain in 50k lines of code means that you now have 500 extra lines of code executed during your test suite. Think about it. Power.
How could it be improved? Here are a few ideas I've had while using Clover this afternoon:
- Locate 'untested hot spots' (ie code which is used frequently but not covered by the test suite)
- Weight the package rankings based package size (ie LOC or some other measure)
- Produce a printable report that can be posted up on the wall and used as a comparison device for progress
(PS Clover is built by Aussies - fantastic)
|
5:20:55 PM |
|
KEN LAYNE:. "Ain't no regime in the world strong enough to deal with an army of pissed-off teen-aged blogger girls." [evhead]
|
11:00:30 AM |
|
Rick tells it all just as well as I could:
Just going through the email, and I noticed that Patrick has released OSWorkflow 2.0. I've been eyeing this for sometime, and yes, the docs have been updated.
Also released, OSCore 2.0.1 and PropertySet 1.0.
Keep up the good work guys! [Rick Salsa]
Great work Patrick. PropertySet 1.0 is a milestone for a very cool, very mature piece of code.
|
10:57:21 AM |
|
|
|
|
|
TOPICS
Home, J2EE, Java, OSX, Open Source, Atlassian, Australia, Blogs

WRITING
View All
LOVE THESE
Atlassian,
IDEA,
OpenSymphony,
Orion,
J2EE,
Webwork,
XDoclet,
Glue,
EXML,
OFBiz,
Google,
Apple,
OSX,
XBox,
Red Hat,
Radio
XML FEEDS

SITES I READ
|