Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show query time in profiler #319

Closed
marijnotte opened this issue Oct 23, 2015 · 4 comments · Fixed by #652
Closed

Show query time in profiler #319

marijnotte opened this issue Oct 23, 2015 · 4 comments · Fixed by #652
Labels

Comments

@marijnotte
Copy link

In dev mode, it would be great to see the query time for each query (like the Doctrine ORM profiler does: http://take.ms/37ILV). This makes it a lot easier to identify queries that are subject for performance improvement.

@alcaeus alcaeus added the Idea label Dec 12, 2015
@ChubV
Copy link
Contributor

ChubV commented Jan 23, 2016

Yeah, to make it happen you have to do something like doctrine/mongodb#153

@jmikola
Copy link
Member

jmikola commented Jul 11, 2018

Note: the command monitoring functionality in the newer mongodb extension may be helpful, as the information could be captured without requiring any modifications to ODM.

@alcaeus alcaeus added this to the 4.0.0 milestone Jul 13, 2018
@alcaeus
Copy link
Member

alcaeus commented Jul 13, 2018

Scheduling for 4.0.0 which will be the first major version to require ODM 2.0, which will require the new driver. We can then finally start implementing this feature. In the meantime, please show your support using emotions instead of +1 comments 😉

@alcaeus alcaeus modified the milestones: 4.0.0-RC1, 4.0.0 Jun 6, 2019
@alcaeus alcaeus removed this from the 4.0.0 milestone Sep 24, 2019
@IonBazan IonBazan linked a pull request Sep 20, 2021 that will close this issue
@IonBazan
Copy link
Member

Implemented in #652 - will be released as 4.4.0 soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants