Mention loading fixtures via symfony console command in README

README.md

@@ -178,6 +178,14 @@ final class MyCustomTest extends BaseKernelTestCase
 }
 ```
 
+To load fixtures in your local environment or as part of a deployment two commands are provided:
+- `neusta:pimcore-fixture:load` (Loads a defined fixture class.)
+- `neusta:pimcore-fixtures:load` (Loads all defined fixture classes.)
+
+Beware that loading a large amount of objects may lead to a high consumption of memory.
+Should you encounter memory issues when running the commands in `dev` environments you may want to try
+setting the environment to `prod`. This appears to be beneficial in terms of pimcore's memory consumption. 
+
 ### Accessing Services from the Fixtures
 
 As the Fixtures are just normal PHP Services you can use all DI features like constructor, setter or property injection as usual.

src/EventListener/PimcoreLoadOptimization.php

@@ -3,6 +3,7 @@
 namespace Neusta\Pimcore\FixtureBundle\EventListener;
 
 use Doctrine\DBAL\Logging\SQLLogger;
+use Neusta\Pimcore\FixtureBundle\Event\AfterExecuteFixture;
 use Neusta\Pimcore\FixtureBundle\Event\AfterLoadFixtures;
 use Neusta\Pimcore\FixtureBundle\Event\BeforeLoadFixtures;
 use Pimcore\Cache;
@@ -29,6 +30,7 @@ public static function getSubscribedEvents(): array
         return [
             BeforeLoadFixtures::class => 'beforeCommand',
             AfterLoadFixtures::class => 'afterCommand',
+            AfterExecuteFixture::class => 'afterExecute',
         ];
     }
 
@@ -52,4 +54,9 @@ public function afterCommand(): void
         $this->versionEnabled && Version::enable();
         $this->cacheEnabled && Cache::enable();
     }
+
+    public function afterExecute(): void
+    {
+        \Pimcore::collectGarbage();
+    }
 }