On Fri, Mar 18, 2011 at 3:57 PM, dmiller wrote:
> No signed assemblies.
>
> What got you below the reported JIT activity into the real problem?
>
> On Mar 18, 11:37 am, Scott Thoman wrote:
>
>> I've had a similar issue unrelated to clojure. In my case we had some
>> signed assemblies and the CLR
On Fri, Mar 18, 2011 at 11:42 AM, dmiller wrote:
> core.clj and company are AOT-compiled. The dll's are loaded during
> startup, not the clojure source.
> When I run a profiler on it during startup, it reports almost all time
> being taken by the JITter.
>
> I'm open to suggestions on improving t
>From what I'm reading about some IronPython tests, it sounds like the
.NET x64 JIT is much slower in startup times. Are we all running 64
bit?
Timothy
> No signed assemblies.
>
> What got you below the reported JIT activity into the real problem?
--
You received this message because you are su
No signed assemblies.
What got you below the reported JIT activity into the real problem?
On Mar 18, 11:37 am, Scott Thoman wrote:
> I've had a similar issue unrelated to clojure. In my case we had some
> signed assemblies and the CLR was taking a long time, in certain
> environments, to go ou
On Fri, Mar 18, 2011 at 11:46 AM, Timothy Baldridge
wrote:
>> I'm open to suggestions on improving this. In particular, more
>> detailed profiling information would be of interest.
>
> Hrm...we have some fairly detailed profilers through my work, so I'll
> have to fire it up over lunch and see wh
> Hrm...we have some fairly detailed profilers through my work, so I'll
> have to fire it up over lunch and see what I get.
Yeah, I'm starting to think dmiller is correct. I went over the
performance traces several times, and it really seems to all revolve
around LoadAssembly, and the time it ta
> I'm open to suggestions on improving this. In particular, more
> detailed profiling information would be of interest.
Hrm...we have some fairly detailed profilers through my work, so I'll
have to fire it up over lunch and see what I get.
timothy
--
You received this message because you are s
core.clj and company are AOT-compiled. The dll's are loaded during
startup, not the clojure source.
When I run a profiler on it during startup, it reports almost all time
being taken by the JITter.
I'm open to suggestions on improving this. In particular, more
detailed profiling information woul
> Just downloaded the CLR version of clojure and are experiencing a
> pretty awkward boot up time of the ClojureMain.exe (~10 sec)
> I've tried to ngen the exe and it's dependencies but without any luck.
> Compiling and Running from within VS2010 it takes approximately the
> same...
Sadly, I thin
Hey All!
Just downloaded the CLR version of clojure and are experiencing a
pretty awkward boot up time of the ClojureMain.exe (~10 sec)
I've tried to ngen the exe and it's dependencies but without any luck.
Compiling and Running from within VS2010 it takes approximately the
same...
Any ideas?
Ch
10 matches
Mail list logo
