RE: Re-2: [ObjectWeb architecture] just an idea for (Java) nativ e compilation

["Leskov, Dmitry" <dleskov@xxxxxxxxxxxxxxxxx>]

> >     As for the server-side apps, am I right in assuming that the disk
> > footprint is usually irrelevant?
> 
> Unfortunately this is not true:
> 
> 1) Many of our customers expect usage of JNLP instead of CD-R for getting
> their software on their client disks. This means, the download size is
> essential. If it is increased thanks to AOT this is a drawback of AOT.
> 
        Well, I meant the apps that are designed to run on the server and
use thin clients. Do you mean your product is a fat client or do you deploy
the server part to end-user systems as well so that it could be used in
off-line mode?

        In any case, you have to choose the right VM(s) for your particular
applications, performance requirements, deployment scenarios, etc. If a VM
with AOT compromises the aspect that is most important for you, surely do
not use that VM. 

> 2) Servers more and more are running on embedded controllers. Memory is
> scarce there.
> 
        That's a good point, however their CPU power is limited as well, and
together these also restrict the quality of JIT-compiled code. So it might
make sense to profile the app and precompile those 10-20% of code that eat
80-90% of CPU time, being it application classes or the ROMized J2ME API. 

        With best regards,

        Dmitry