GTG

Update boot-up performance option

Bug #897438 reported by Izidor Matušov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Critical
Izidor Matušov

Bug Description

Instead of running it only through a single iteration, it should wait until all tasks are loaded and after that immediately finish. The change is needed because of the change of LibLarch.

Solving this bug may facilitate tackling the performance issue on load.

Do not forget to update manpage documentation.

Related branches

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

I don't understand what you mean here. What should be done to fix this bug?

Revision history for this message
Izidor Matušov (izidor) wrote :

The current implementation of -b is to instead of gtk.main() run gtk.main_iteration(). Before LibLarch it means that GTG finished when the first idle situation occurred (everything was loaded)

Because of the change of LibLarch (it is asynchronous and process requests during those idle states), the implementation does not make sense and must be changed.

I believe that the feature was implemented because of profiling boot-up performance -- when everything was loaded, GTG finished and the measurement was not influenced by human factor (Is it already finished or not yet?)

Reworking this feature can help during performance optimization.

Izidor Matušov (izidor)
Changed in gtg:
assignee: nobody → Izidor Matušov (izidor)
status: Confirmed → In Progress
Revision history for this message
Izidor Matušov (izidor) wrote :

Merged at rev 1177

Changed in gtg:
status: In Progress → Fix Committed
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.