search

civicrm / org.civicrm.api4

CiviCRM api version 4
Other
8 stars 19 forks source link

Design Principles: add "Tunable" #19

Open ErichBSchulz opened 7 years ago

ErichBSchulz commented 7 years ago

IMHO, in order to optimise the API and CiviCRM more broadly we need solid data on what tasks are taking up time

this maybe bigger than API4 but seems to me that capturing and logging performance data is a criticial requirement

so yet another one I'd like a +1 or -1 on...

I sketched a rough plan here of what this could look like and why its worth doing.

JoeMurray commented 7 years ago

I think the issues here are political/security oriented more than technical. I would also be very reluctant to add any new dependencies on the CiviCRM server and hesitant about bulking up the tarball with big new libraries.

xurizaemon commented 7 years ago

Definitely do not recommend shipping performance / tuning libs (uncertain if that was the proposal). Discussion over in Google doc was more "let's use existing available tools to analyse performance" than "let's ship performance profiling with CiviCRM".