[Profiling] Identifying the bottlenecks in Enforcer

[EmperorYP7]

Description

With reference to #176, it was found that casbin::Enforcer is performing significantly worse for RBAC workflows than its Golang counterparts. We need to implement profiling throughout the project to identify bottlenecks.

Screenshots/Testimonials

[casbin-bot]

@EmperorYP7 @divy9881 @noob20000405 @sheny1xuan

[hsluoyz]

@sheny1xuan plz work on this as next step

[sheny1xuan]

Hi, I have do some profiling for casbin-cpp using calgrind, and I can't include it in the existing CI workflows too. You can find my code in my repo.
In a normal rbac enforce process, InitializeScope for duktape expression evaluator costs too much time. I think each enforcer can hold a Scope rather than InitializeScope when enforce a request.
What do you think? @EmperorYP7 @hsluoyz .

[EmperorYP7]

In a normal rbac enforce process, InitializeScope for duktape expression evaluator costs too much time. I think each enforcer can hold a Scope rather than InitializeScope when enforce a request.

I was suspecting that to be the bottleneck, we need to work our way around it. Having a separate Scope for each call of Enforce is unnecessary.

[github-actions]

🎉 This issue has been resolved in version 1.44.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀