The number of queries is displayed in the webdebug tool bar. Maybe we should also show the number of services instanciated in the tool bar? This way people could maybe notice if a dependency they have added is causing a spike in used services? Obviously not every service is equally expensive, but the same applies to queries. It can also help in getting an idea of how useful turning a specific service to a proxy is.
showing only the number of services might not help you much about knowing which one is the culprit. And https://github.com/schmittjoh/JMSDebuggingBundle is providing tracing of the container usage
right .. like i said .. knowing the number is likely only useful if you notice the change in the number right after doing a specific change. so yes having some more help in the profiler with additional details will then also be necessary to fix the issue in many situations.
needed more thinking and explanation, but this is not bad idea
Good idea, dependency graph in Web Debug Toolbar would be a nice improvement.
Having the number of instancied services in the toolbar, why not, but maybe we could push it further, and having a sort of a "DIC" panel in the profiler ?
@Taluu See the link I gave above
Yeah but maybe something more than a graph ? Like detailed stats on the startup on a service, ... this kind of stuff
@Taluu Look at the different tabs of the DebuggingBundle. It allows you to list all calls to retrieve a service from the container, assuming you enabled the traceable container in your app.
Closing as there is a bundle doing something similar and also because the number of services does not tell you the whole story as a service can also create many instances of non-services.