摘要：大家都知道項目寫起來是挺爽，但是在生產(chǎn)環(huán)境性能不高，我們來抽絲剝繭分析我自己項目的運行時間消耗耗時步驟耗時觀察初步結論在調(diào)用和的方法時，消耗時間是大頭。類是用于注冊服務提供者的。但此優(yōu)化在下無效。我們進一步分析。

大家都知道 laravel 項目寫起來是挺爽，但是在生產(chǎn)環(huán)境性能不高，我們來抽絲剝繭分析我自己項目的運行時間消耗：

觀察初步結論： laravel 在調(diào)用 IlluminateFoundationBootstrapRegisterProviders 和 IlluminateFoundationBootstrapBootProviders 的 bootstrap 方法時，消耗時間是大頭。

類 IlluminateFoundationBootstrapRegisterProviders 是用于注冊服務提供者的。

類 IlluminateFoundationBootstrapBootProviders 是用于啟動服務提供者的。

laravel 的內(nèi)置server php artisan serve 自帶了優(yōu)化機制，上面數(shù)據(jù)僅體現(xiàn)首次加載的耗時。二次加載時會相比少很多。但此優(yōu)化在 fpm 下無效。

我們進一步分析。

IlluminateFoundationBootstrapRegisterProviders::bootstrap 方法代碼如下：

    /**
     * Bootstrap the given application.
     *
     * @param  IlluminateFoundationApplication  $app
     * @return void
     */
    public function bootstrap(Application $app)
    {
        $app->registerConfiguredProviders();
    }

所以我們還是回到了 IlluminateFoundationApplication 這個文件：

    /**
     * Register all of the configured providers.
     *
     * @return void
     */
    public function registerConfiguredProviders()
    {
        $providers = Collection::make($this->config["app.providers"])
                        ->partition(function ($provider) {
                            return Str::startsWith($provider, "Illuminate");
                        });

        $providers->splice(1, 0, [$this->make(PackageManifest::class)->providers()]);

        (new ProviderRepository($this, new Filesystem, $this->getCachedServicesPath()))
                    ->load($providers->collapse()->toArray());
    }

針對上面的 (new ProviderRepository)->load 進行耗時分析發(fā)現(xiàn)數(shù)據(jù)為

毋庸置疑這就是消耗時間的大頭。

里面的代碼為

    /**
     * Register the application service providers.
     *
     * @param  array  $providers
     * @return void
     */
    public function load(array $providers)
    {
        $manifest = $this->loadManifest();

        // First we will load the service manifest, which contains information on all
        // service providers registered with the application and which services it
        // provides. This is used to know which services are "deferred" loaders.
        if ($this->shouldRecompile($manifest, $providers)) {
            $manifest = $this->compileManifest($providers);
        }

        // Next, we will register events to load the providers for each of the events
        // that it has requested. This allows the service provider to defer itself
        // while still getting automatically loaded when a certain event occurs.
        foreach ($manifest["when"] as $provider => $events) {
            $this->registerLoadEvents($provider, $events);
        }

        // We will go ahead and register all of the eagerly loaded providers with the
        // application so their services can be registered with the application as
        // a provided service. Then we will set the deferred service list on it.
        foreach ($manifest["eager"] as $provider) {
            $this->app->register($provider);
        }

        $this->app->addDeferredServices($manifest["deferred"]);
    }

而再經(jīng)過定位，發(fā)現(xiàn)慢在這一行

        foreach ($manifest["eager"] as $provider) {
            $this->app->register($provider);
        }

又回到 IlluminateFoundationApplication

    /**
     * Register a service provider with the application.
     *
     * @param  IlluminateSupportServiceProvider|string  $provider
     * @param  array  $options
     * @param  bool   $force
     * @return IlluminateSupportServiceProvider
     */
    public function register($provider, $options = [], $force = false)
    {
        if (($registered = $this->getProvider($provider)) && ! $force) {
            return $registered;
        }

        // If the given "provider" is a string, we will resolve it, passing in the
        // application instance automatically for the developer. This is simply
        // a more convenient way of specifying your service provider classes.
        if (is_string($provider)) {
            $provider = $this->resolveProvider($provider);
        }

        if (method_exists($provider, "register")) {
            $provider->register();
        }

        // If there are bindings / singletons set as properties on the provider we
        // will spin through them and register them with the application, which
        // serves as a convenience layer while registering a lot of bindings.
        if (property_exists($provider, "bindings")) {
            foreach ($provider->bindings as $key => $value) {
                $this->bind($key, $value);
            }
        }

        if (property_exists($provider, "singletons")) {
            foreach ($provider->singletons as $key => $value) {
                $this->singleton($key, $value);
            }
        }

        $this->markAsRegistered($provider);

        // If the application has already booted, we will call this boot method on
        // the provider class so it has an opportunity to do its boot logic and
        // will be ready for any usage by this developer"s application logic.
        if ($this->booted) {
            $this->bootProvider($provider);
        }

        return $provider;
    }

在 register 方法中，根據(jù) get_class($provider) 和 執(zhí)行耗時，得出以下數(shù)據(jù)

得出 RegisterProviders 瓶頸的結論

AppProvidersResponseMacroServicePrivoder 占用 37ms

DingoApiProviderLaravelServiceProvider 占用 20ms

IlluminateDatabaseDatabaseServiceProvider 占用 9ms

OvertrueLaravelWeChatServiceProvider 占用 9ms

EasyWeChatComposerLaravelServiceProvider::boot 的啟動速度，略慢，分析原因： 代碼 Github boot 方法中，加載了路由。而 Laravel 的路由，確實是比較慢的。

[未完]