base on ★ Laravel Slower: Optimize Your DB Queries with AI # Laravel Slower: Optimize Your DB Queries with AI [](https://packagist.org/packages/halilcosdu/laravel-slower) [](https://github.com/halilcosdu/laravel-slower/actions?query=workflow%3Arun-tests+branch%3Amain) [](https://github.com/halilcosdu/laravel-slower/actions?query=workflow%3A"Fix+PHP+code+style+issues"+branch%3Amain) [](https://packagist.org/packages/halilcosdu/laravel-slower) <a href="https://trendshift.io/repositories/10023" target="_blank"><img src="https://trendshift.io/api/badge/repositories/10023" alt="halilcosdu%2Flaravel-slower | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a> Laravel Slower is a powerful package designed for Laravel developers who want to enhance the performance of their applications. It intelligently identifies slow database queries and leverages AI to suggest optimal indexing strategies and other performance improvements. Whether you're debugging or routinely monitoring your application, Laravel Slower provides actionable insights to streamline database interactions. ## Installation You can install the package via composer: ```bash composer require halilcosdu/laravel-slower ``` You can publish the config file with: ```bash php artisan vendor:publish --tag="slower-config" ``` This is the contents of the published config file: You can disable AI recommendations by setting the `ai_recommendation` key to `false` in the config file. If you disable AI recommendations, the package will not make any API requests to OpenAI. ```php <?php // config for HalilCosdu/Slower use HalilCosdu\Slower\Models\SlowLog; return [ 'enabled' => env('SLOWER_ENABLED', true), 'threshold' => env('SLOWER_THRESHOLD', 10000), 'resources' => [ 'table_name' => (new SlowLog)->getTable(), 'model' => SlowLog::class, ], 'ai_recommendation' => env('SLOWER_AI_RECOMMENDATION', true), 'recommendation_model' => env('SLOWER_AI_RECOMMENDATION_MODEL', 'gpt-4'), 'recommendation_use_explain' => env('SLOWER_AI_RECOMMENDATION_USE_EXPLAIN', true), 'ignore_explain_queries' => env('SLOWER_IGNORE_EXPLAIN_QUERIES', true), 'ignore_insert_queries' => env('SLOWER_IGNORE_INSERT_QUERIES', true), 'open_ai' => [ 'api_key' => env('OPENAI_API_KEY'), 'organization' => env('OPENAI_ORGANIZATION'), 'request_timeout' => env('OPENAI_TIMEOUT'), ], 'prompt' => env('SLOWER_PROMPT', 'As a distinguished database optimization expert, your expertise is invaluable for refining SQL queries to achieve maximum efficiency. Schema json provide list of indexes and column definitions for each table in query. Also analyse the output of EXPLAIN ANALYSE and provide recommendations to optimize query. Please examine the SQL statement provided below including EXPLAIN ANALYSE query plan. Based on your analysis, could you recommend sophisticated indexing techniques or query modifications that could significantly improve performance and scalability?'), ]; ``` You can publish and run the migrations with: ```bash php artisan vendor:publish --tag="slower-migrations" ``` ```bash php artisan migrate ``` ```php public function up() { Schema::create(config('slower.resources.table_name'), function (Blueprint $table) { $table->id(); $table->boolean('is_analyzed')->default(false)->index(); $table->longtext('bindings'); $table->longtext('sql'); $table->float('time')->nullable()->index(); $table->string('connection'); $table->string('connection_name')->nullable(); $table->longtext('raw_sql'); $table->longtext('recommendation')->nullable(); $table->timestamps(); }); } public function down(): void { Schema::dropIfExists(config('slower.resources.table_name')); } ``` ## Usage You can register the commands with your scheduler. ```php php artisan slower:clean /*{days=15} Delete records older than 15 days.*/ php artisan slower:analyze /*Analyze the records where is_analyzed=false*/ ``` ```php use HalilCosdu\Slower\Commands\AnalyzeQuery; use HalilCosdu\Slower\Commands\SlowLogCleaner; protected $commands = [ AnalyzeQuery::class, SlowLogCleaner::class, ]; /** * Define the application's command schedule. */ protected function schedule(Schedule $schedule): void { $schedule->command(AnalyzeQuery::class)->runInBackground()->daily(); $schedule->command(SlowLogCleaner::class)->runInBackground()->daily(); } ``` ```php $model = \HalilCosdu\Slower\Models\SlowLog::first(); \HalilCosdu\Slower\Facades\Slower::analyze($model): Model; dd($model->raw_sql); /*select count(*) as aggregate from "product_prices" where "product_id" = '1' and "price" = '0' and "discount_total" > '0'*/ dd($model->recommendation); ``` ### Example Screen <a href="https://i.ibb.co/J2xvB1y/Screenshot-2024-05-11-at-00-24-52.png"> <img src="https://i.ibb.co/J2xvB1y/Screenshot-2024-05-11-at-00-24-52.png" alt="Screenshot" style="width:100%;"> </a> ### Example Recommendation In order to improve database performance and scalability, here are some suggestions below: 1. Indexing: Effective database indexing can significantly speed up query performance. For your query, consider adding a combined (composite) index on `product_id`, `price`, and `discount_total`. This index would work well because the where clause covers all these columns. ```sql CREATE INDEX idx_product_prices ON product_prices (product_id, price, discount_total); ``` (Note: The order of the columns in the index might depend on the selectivity of the columns and the data distribution. Therefore, you might have to reorder them depending on your specific situation.) 2. Data Types: Ensure that the values being compared are of appropriate data types. Comparing or converting inappropriate data types at run time will slow down the search. It appears that you're using string comparisons ('1') for `product_id`, `price`, and `discount_total` which are likely numerical columns. Remove the quotes for these where clause conditions. Updated Query: ```sql SELECT COUNT(*) AS aggregate FROM product_prices WHERE product_id = 1 AND price = 0 AND discount_total > 0; ``` 3. ANALYZE: Another practice to improve query performance could be running the `ANALYZE` command. This command collects statistics about the contents of tables in the database, and stores the results in the pg_statistic system catalog. Subsequently, the query planner uses these statistics to help determine the most efficient execution plans for queries. ```sql ANALYZE product_prices; ``` Remember to periodically maintain your index to keep up with the CRUD operations that could lead to index fragmentation. Depending on your DBMS, you might want to REBUILD or REORGANIZE your indices. ## Testing ```bash composer test ``` ## Roadmap - [ ] Create a documentation page. - [ ] Begin development of version 2. - [ ] Auto Indexer (Premium Feature) - [ ] Create a FilamentPHP plugin. ## Changelog Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently. ## Contributing Please see [CONTRIBUTING](CONTRIBUTING.md) for details. ## Security Vulnerabilities Please review [our security policy](../../security/policy) on how to report security vulnerabilities. ## Credits - [Halil Cosdu](https://github.com/halilcosdu) - [All Contributors](../../contributors) ## License The MIT License (MIT). Please see [License File](LICENSE.md) for more information. ", Assign "at most 3 tags" to the expected json: {"id":"10023","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"