Project

General

Profile

Actions

Bug #2125

closed

Make rudder starts quicker

Added by François ARMAND over 12 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
4
Category:
Architecture - Code maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

There is a lot of time eaten at Rudder start-up, has seen here:
1/ http://pastie.org/private/yhzxt0b3dhf0uxerewys6a
2/ http://pastie.org/private/nqzlsxvrd6iuuaopekqrg

In 1/ we see that 1 minute is spend between the first two lines, and again 2 minutes at the end.

The last two minutes seems to be used by all the (normally asynchronous) batch taking place during start-up, and they take a lot of time. Moreover, that is likelly to hardly stress the database, as a lot of things are ask to it at that moment.

On the other hand, we see that there is a lot of crap in our (outadated) Jetty server. Most "deployable" elements should be removed, as we only really need endpoint.war and rudder.war here.

So, two action should be taken:
1/ clean-up Jetty configuration
2/ delay all asynchronous service until full init is done, and perhaps randomized a little the first start of these batch.


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Architecture #3270: Remove Spring for most of service bindingReleasedFrançois ARMAND2013-02-18Actions
Actions

Also available in: Atom PDF