Re: Native sFTP?

["Richard Schoen" <richard@xxxxxxxxxxx>]

It might be because it renders with AWT I believe, however that doesn't
change the fact that it is SLOOOOOW natively :-)

Some pure Java routines run just fine natively.

Regards,
Richard Schoen
RJS Software Systems Inc. 
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

------------------------------

message: 5
date: Mon, 27 Apr 2009 10:49:26 -0700 (PDT)
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: Re: Native sFTP?


> From: Richard Schoen
> We use Jasper Reports quite heavily and a 5 page document that takes
> 30-60+ seconds when running Jasper natively takes 1-3 seconds when
> we job it out to a PC.

Could that be due to some architectural bottleneck besides CPU - elapsed
time to start a JVM from scratch, for example?

I was just looking at SPEC J2EE benchmarks and noted that when you
compare core-to-core, cpu-to-cpu, Power outperformed Intel XEON.  For
example, a 4-core/2-CPU Power 570 compared to a Dell 4-core/2-CPU XEON
X5260:

http://www.spec.org/jbb2005/results/jbb2005.html

Nathan.