Long query time

[staudenmeir]

Long query time

[staudenmeir]

Can you run EXPLAIN with the last query?

How many records does server_stats have per server_id (on average)?

Have you tried the query without the limit?

[igunultas]

Here is the EXPLAIN result

well i just deleted unnecessary rows in order to reduce query timing but not effected the way it works, most likely right know 60K rows for each server_id

without limit server drops connection :P i think its related to my database not to package :(

[staudenmeir]

Can you post the migration of server_stats or its table structure in the database (with indexes)?

[igunultas]

of course

here is the migration

 public function up()
    {
        Schema::create('server_stats', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->integer("server_id");
            $table->json("cpu");
            $table->json("ram");
            $table->json("swap");
            $table->json("disk");
            $table->json("network");
            $table->json("cpustats");
            $table->timestamps();
        });
    }

[staudenmeir]

Please add an index to server_id and try again.

[igunultas]

I did here is the explain result and the query still takes 1 min 3 seconds

if you want to dig deeper you can connect my computer over anydesk or teamviewer

[staudenmeir]

Could you send me a dump of the whole table or does it contain any sensitive data?

[igunultas]

DATA REMOVED FOR PRIVACY

here is the data of server_stats table

i would love to send servers table as well but it contains sensetive data

there is 10 rows in servers table from (1 to 10). 9 does not have any information in server_stats table.

[staudenmeir]

I've looked into it, but I couldn't figure out why MariaDB isn't using the index.

Since this is the standard implementation of such a query, the issue is not caused by the package.

I suggest that you ask a question on Stack Overflow.

[igunultas]

Thank you for your effort and time :)