On Mon, Sep 20, 2010 at 7:26 AM, Jo Størset wrote:
>
>
> 2010/9/18 Lars Helge Øverland
>
>
>> Can't really believe it but it seems Spring auto-wiring was the problem.
>> Disabled it and went back to normal XML based wiring and Live now starts in
>> 26 seconds at my Ubuntu laptop.
>>
>
> It seems
2010/9/18 Lars Helge Øverland
>
> Can't really believe it but it seems Spring auto-wiring was the problem.
> Disabled it and went back to normal XML based wiring and Live now starts in
> 26 seconds at my Ubuntu laptop.
>
It seems the bean factory doesn't cache anything by type [1], so I guess by
Can't really believe it but it seems Spring auto-wiring was the problem.
Disabled it and went back to normal XML based wiring and Live now starts in
26 seconds at my Ubuntu laptop.
Have committed the change to 2.0.5 branch, will merge into trunk when I have
time.
Lars
__
2010/9/17 Lars Helge Øverland
>
>
> 2010/9/17 Saptarshi Purkayastha
>
> wow... that is loon.
>> I have been doing all the stuff on Live using my 2.0.4 indian modules and
>> it starts in ~25 seconds and switching or blank database happens in
>> 16secs... and was super happy with the speed
>>
2010/9/17 Saptarshi Purkayastha
> wow... that is loon.
> I have been doing all the stuff on Live using my 2.0.4 indian modules and
> it starts in ~25 seconds and switching or blank database happens in
> 16secs... and was super happy with the speed
>
> But 1:25 is quiet slow.
>
> I've heard of
wow... that is loon.
I have been doing all the stuff on Live using my 2.0.4 indian modules and it
starts in ~25 seconds and switching or blank database happens in 16secs...
and was super happy with the speed
But 1:25 is quiet slow.
I've heard of memory issues on Spring 3 migrations:
https://j
I have tracked the problem of slow starting of Live on linux to somewhere
between revision 1818 and 1823. Here we upgraded Spring from 2 to 3 and
Struts from 1.6 to 1.8.1. Also, Abyot merged in work on sections from his
branch.
I have disabled Spring classpath scanning for components. (We still ha
2010/9/16 Bob Jolliffe
> the main difference is that the live version runs with exploded war.
> this was to improve startup time on old machines - which it really
> did.. It might well be this is now working against us. not sure how
> but its the main factor i can think of.
Not sure if that's
the main difference is that the live version runs with exploded war.
this was to improve startup time on old machines - which it really
did.. It might well be this is now working against us. not sure how
but its the main factor i can think of.
2010/9/16 Lars Helge Øverland :
>
> Seems we can che
Seems we can check the Live package out of the case
I checked out revision 1412 and built both Live and WAR. Started in 29 sec.
I then ran the latest Live with the old (r1412) WAR and it started in 29 sec
too. The latest Live and latest WAR starts in 1 min 45 sec. So there's got
to be somethin
Might not be relevant, but I can see we are using custom multi-threading in
combination with swing/awt, doesn't seem like a great idea:
http://download.oracle.com/javase/tutorial/uiswing/concurrency/dispatch.html
http://weblogs.java.net/blog/kgh/archive/2004/10/multithreaded_t.html
___
performs fine but slow startup
2010/9/16 Lars Helge Øverland :
>
> Bob, how is Live performing on your Ubuntu ?
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-d
Bob, how is Live performing on your Ubuntu ?
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
2010/9/16 Bob Jolliffe
> 2010/9/16 Lars Helge Øverland :
> >
> > It seems this happens on Linux only.
> > My startup time on Tomcat is 29 seconds. The added 4 seconds is due to
> the
> > change to using Spring annotations and classpath scanning (didn't think
> of
> > that but not such a big deal)
2010/9/16 Lars Helge Øverland :
>
> It seems this happens on Linux only.
> My startup time on Tomcat is 29 seconds. The added 4 seconds is due to the
> change to using Spring annotations and classpath scanning (didn't think of
> that but not such a big deal).
OK. I think that is good news ie. it
It seems this happens on Linux only.
My startup time on Tomcat is 29 seconds. The added 4 seconds is due to the
change to using Spring annotations and classpath scanning (didn't think of
that but not such a big deal). For me it also takes more than a minute to
start with Live. This was not the cas
Hi,
Yes, Bob. You are right in this issue. The reason of this one is that DHIS2
is during on development. Thus, when we could not avoid some of mistakes or
fixing or changing the data model in it. Thought that, this problem can be
resolve if and only if all of instances of DHIS2 (I meant the local
I have certainly noticed the veeery sluggish startup of recent builds.
It makes DHIS2 Live much less attractive, unfortunately.
Knut
On Thu, Sep 16, 2010 at 6:51 PM, Bob Jolliffe wrote:
> I don't know if anyone has seen a slowing in startup time in recent
> months. I recall about a year ago we
I don't know if anyone has seen a slowing in startup time in recent
months. I recall about a year ago we had startup down to about 25s.
These days my startup time is looking abysmal again. Approx 1 minute
between setting dhis2 home and beginning to execute the startup
routines. Is anyone else see
19 matches
Mail list logo
