Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COYes I was just reading the docs of Silex, but it turns out to be too small :D I would like to take advantage of the fos/knp symfony bundles though.. I figured out how to disable monolog, but again, it turned out that monolog wasn't causing almost any overhead. Any other lightweight-ifying tips?
      singulars
    2. COWell, I can't say anything without seeing how your project is performing. The Symfony2 base code is already fast and micro optimised in lots of areas. Fabien Potencier, the creator of Symfony, has a series of blog posts in his blog (http://fabien.potencier.org/) , explaining building a framework with Symfony components. You can check them to understand how Symfony works, than you can only use the components you really need to improve performance further. You can use the debug toolbar and profiler to look for bottlenecks and improve the code to remove them.
      singulars
    3. COI guess I shouldn't worry about it. I already have a medium heavy project based on symfony 2 (not very good coded - it's my first), which usually takes 50-60 ms to load on the prod server. The whole problem comes from the fact that at my laptop (in dev env) the plain Acme Demo bundle takes >1s to load, which is quite slow for development. The other project goes as far as 4s with my code, still I guess it's better to optimize the bundle and the server, or pay for additional CPU power rather than searching for ways to optimize what's already optimized to the limit (Symfony 2). Thanks!
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload