graph_ensemble_learning icon indicating copy to clipboard operation
graph_ensemble_learning copied to clipboard
verified publisher icon IBM

Slow Graphene_Smatch

Open Zoher15 opened this issue 2 years ago • 5 comments

Hi @lamthuy,

I found that 'vote' and 'graphene' are really quick but 'graphene_smatch' is incredibly slow. It takes hours.... Would you know why that is?

Best, Zoher

Zoher15 avatar May 31 '23 18:05 Zoher15

In graphene_smatch, after modifying each graph in the ensemble similar to the graphene option, it needs to do an extra calculation of the smatch between the modified graph and all other graphs. That step is more expensive if the number of graph in the ensemble is large.

lamthuy avatar Jun 01 '23 06:06 lamthuy

I am only using three parsers for the ensemble....

Zoher15 avatar Jun 01 '23 06:06 Zoher15

@lamthuy MBSE also does the same thing right? I am still not sure why graphene_smatch is so much slower in comparison when I am using the same number of graphs in the ensemble for both. Or maybe I am missing something?

Zoher15 avatar Jun 12 '23 16:06 Zoher15

@lamthuy Is it because you have to recalculate the pairwise smatch for each pivot o(n^3) whereas MBSE you only need a single o(n^2) calculation?

Zoher15 avatar Jun 12 '23 18:06 Zoher15

If there are only 3 models it should not be that slow, I have a deadline now, will take a look when I am back.

lamthuy avatar Jun 12 '23 19:06 lamthuy