search

mfrey / baltimore

baltimore is an analysis script for the libARA framework
GNU General Public License v3.0
0 stars 0 forks source link

Make routing table data parsing optional #27

Closed fgrosse closed 11 years ago

fgrosse commented 11 years ago

Parsing of the binary routing table data is very time consuming and should be optional. i also think it should be disabled by default and should be activated via the configuration file

mfrey commented 11 years ago

I've added a new section in the configuration file, called 'Analysis'. There is an option 'routing_table_trace' which can be set to true/false, 0,1 or on/off and enables or disables the analysis of routing table traces. I've also checked the performance of the analysis time-wise with enabled and disabled trace analysis.

Execution time with enabled trace

[frey@pandora baltimore]$ time ./main.py -c baltimore.ini
....
Successfully read 1 experiment(s) from 5 scalar file(s).

real  0m2.946s
user  0m2.772s
sys   0m0.068s

Execution time with disabled trace

[frey@pandora baltimore]$ time ./main.py -c baltimore.ini
....
Successfully read 1 experiment(s) from 5 scalar file(s).

real  0m44.394s
user  0m39.188s
sys   0m0.304s
fgrosse commented 11 years ago

Wow those timings seem way to high. Assuming you had 50 nodes you would have to read 250 files and create 250 plots from that. I would be guessing most of the time is lost when creating the plots...

mfrey commented 11 years ago

You think we have another issue?

"Friedrich Große" notifications@github.com schrieb:

Wow those timings seem way to high. Assuming you had 50 nodes you would have to read 250 files and create 250 plots from that. I would be guessing most of the time is lost when creating the plots...

Reply to this email directly or view it on GitHub: https://github.com/mfrey/baltimore/issues/27#issuecomment-19611358

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.