You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm planning to use your SLHAea package in my own spectrum generator because it looks very elegant and seems to be easy to use.
However, speed is a critical point for me, so I wonder how SLHAea performs compared to SLHALib (http://www.feynarts.de/slha/) or other hand-written SLHA libraries? My wish would be that reading and writing time together is much smaller than 0.1 ms. Have you done some speed comparisons with other libraries?
There is one problematic point which I have in mind: You are using std::string as map key in your examples:
It could be that this is rather slow compared to an integer key (depending on the std::map implementation). So, using enums as an alternative would probably help here.
One possibility to achieve this would be to make the key type a template parameter which can be chosen by the user at compile time
after looking into your code and studying the SLHA standard a bit, I think my above proposal doen not make much sense. This is because the SLHA standard allows user-defined blocks, which cannot be handled by an enum which you use as template parameter.
Dear Frank Thomas,
I'm planning to use your SLHAea package in my own spectrum generator because it looks very elegant and seems to be easy to use.
However, speed is a critical point for me, so I wonder how SLHAea performs compared to SLHALib (http://www.feynarts.de/slha/) or other hand-written SLHA libraries? My wish would be that reading and writing time together is much smaller than 0.1 ms. Have you done some speed comparisons with other libraries?
There is one problematic point which I have in mind: You are using
std::string
as map key in your examples:It could be that this is rather slow compared to an integer key (depending on the
std::map
implementation). So, using enums as an alternative would probably help here.One possibility to achieve this would be to make the key type a template parameter which can be chosen by the user at compile time
What do you think about this option?
Best regards,
Alexander Voigt
The text was updated successfully, but these errors were encountered: