| View Issue Details [ Jump to Notes ] [ Related Changesets ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000180 | Frama-C | Kernel | public | 2009-07-09 19:38 | 2014-02-12 16:57 |
|
| Reporter | dpariente | |
| Assigned To | pascal | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | Frama-C GIT, precise the release id | |
| Target Version | | Fixed in Version | Frama-C Beryllium-20090901 | |
|
| Summary | 0000180: Save/Load elapsed time |
| Description | Hello,
A state is saved after a simple value analysis:
frama-c -val -slevel 0 -main M file.c -save state.sav
file.c is about 12 ksloc.
This analysis takes about 15 minutes.
Simply loading the previously generated state.sav file:
frama-c -load state.sav
takes about 18 minutes.
A loading time being greater than the analyzing+saving time is quite puzzling!
An analysis recommended by some of Frama-C's experts showed that most of the elapsed time was due to value_table deserializing.
What can be done to improve loading time?
Regards,
Dillon
(P.S. : Rel.id>=5634)
|
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships