[IMP] core: populate CLI improvements

[Feyensv]

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

[robodoo]

[Feyensv]

@Xavier-Do Don't you think it could be useful to integrate the profiling feature directly into the populate script ? (And eventually the rollback part, but I can drop it, it's less useful).

[Xavier-Do]

Forgot my last message, I didn't look at the diff. I don't have any objections if it is opt-in :) But keep in mind that the default profiler parameters includes the sql collector witch have an impact for a lot of fast queries. It would be great to have a way to define what we want to profile. I also wonder if a --profile option isn't too generic we may want to add that to odoo-bin some day.

Those comments are just ideas the current solution looks great!

[Feyensv]

But keep in mind that the default profiler parameters includes the sql collector witch have an impact for a lot of fast queries. It would be great to have a way to define what we want to profile.

As I see it, when you use the profiler, you should limit yourself to the small (/medium) population size, since you'll globally have the same results and perf bottlenecks when investigating the creation of X records instead of X*10 records. (I even think I got some strange errors while trying profiling & rollback on complex models/sizes).
I could add a choice of profilers, but I think it would be too much noise when most people always enable/use all the profilers at once.

I also wonder if a --profile option isn't too generic we may want to add that to odoo-bin some day.

I don't have a better option in mind (and --populate-profile is overkill imho).
Can't we consider this usecase when we really want to add an option in the generic command ?

[tde-banana-odoo]

Is there any human readable summary :D ?

[Feyensv]

1. odoo-bin populate --profile to Create ir.profile record for each model population (to have a speedscope to investigate)
2. odoo-bin populate --rollback to avoid having to drop the db/copy a template db between two populate calls (Example, you cannot populate res.company twice on a db because of constraints on the model). With this, you could trigger the populate multiple times more easily to see the impact of code changes :).

[Feyensv]

@robodoo r+

[Feyensv]

@robodoo rebase-ff

[robodoo]

Merge method set to rebase and fast-forward