Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Frama-C: GUI's response time

  • Subject: [Frama-c-discuss] Frama-C: GUI's response time
  • From: Dillon.Pariente at dassault-aviation.com (Pariente Dillon)
  • Date: Wed, 22 Apr 2009 11:21:27 -0000
  • In-reply-to: <038BAD36-8FFD-4957-97B6-E6B490C95857@cea.fr>
		 
		When launching frama-c-gui -load my_state.sav, elapsed
time is about 30 minutes, before Frama-C-GUI window is displayed.

	
	
	This is interesting. What is the time taken by "frama-c -load
my_state.sav" 
	(that is, the same command for the non-GUI version) for the same
state?

 
10 min 30 sec
 



	If it is long, the problem is in the functions that reload the
value analysis' state.
	This has happened before. When this kind of bug manifests
itself, 
	it may be much slower to reload the state from disk than to
compute it again
	from scratch.
	
	
	If the time is short, the problem is definitely in how the GUI
scales.
	
	
	It could also help to measure the times taken by each of
	the following commands:
	
	
	frama-c -save no_analysis.sav *.c   # no option that would cause
the value analysis to run

 
0 min 8 sec



	frama-c-gui -load no_analysis.sav

0 min 8 sec
 



	frama-c -load no_analysis.sav

0 min 0.4 sec
 
To sum up, 1/3 of elapsed time seems to be due to the loading of
functions +/-"stricto sensu", 2/3 due to the GUI, that's it?
 
Best regards,
Dillon
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20090422/67054150/attachment-0001.htm