Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-03 Thread Chas Emerick
On Jan 2, 2011, at 9:13 AM, Marek Kubica wrote: But in theory it could be posible to collect run-time data in one run, then JIT code at startup, using that collected data and current procesor architecture. Something like this is already used in practice, it is called Profile-Guided

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-02 Thread Konrad Hinsen
On 2 Jan 2011, at 03:29, Sunil S Nandihalli wrote: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary? I would not mind jitting the whole code .. Actually I don't mind waiting a few

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-02 Thread Sunil S Nandihalli
thanks you all for your feedback .. but I had implemented something in clojure which I knew would be much faster in say c++ .. and now was regretting it .. and was really looking at all weird locations in desperation.. but now I realized I was doing something in a very wrong inefficient

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-02 Thread ajuc
On 2 Sty, 12:01, Konrad Hinsen konrad.hin...@fastmail.net wrote: On 2 Jan 2011, at 03:29, Sunil S Nandihalli wrote:  can I force the JIT to be called immediately for certain pieces of   code after it starts executing with out waiting for the JVM realize   it is necessary? I would not

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-02 Thread Marek Kubica
On Sun, 2 Jan 2011 05:41:08 -0800 (PST) ajuc aju...@gmail.com wrote: But in theory it could be posible to collect run-time data in one run, then JIT code at startup, using that collected data and current procesor architecture. Something like this is already used in practice, it is called

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-02 Thread Alex Miller
You can change the number of times code must be run before it is compiled with this flag: -XX:CompileThreshold=1 The default is 1500 in the client hotspot and 1 in server hotspot. Of course, you should probably not muck with this unless you are feeling kinda wild and crazy. On Jan 1,

can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-01 Thread Sunil S Nandihalli
Hello Everybody, can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary? I would not mind jitting the whole code .. Actually I don't mind waiting a few extra seconds at the start since actual

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-01 Thread Brian Goslinga
On Jan 1, 8:29 pm, Sunil S Nandihalli sunil.nandiha...@gmail.com wrote: Hello Everybody,  can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary? I would not mind jitting the whole code ..

Re: can I force the JIT to be called immediately for certain pieces of code after it starts executing with out waiting for the JVM realize it is necessary....

2011-01-01 Thread Daniel Gagnon
Even if the JVM put the code through the compiler right away, the resulting code wouldn't be very good because it will have not had time to profile code to apply the more powerful optimizations. It would be throwing all of that code away once it has had time to profile the code, so any time