Please, optimize table structure of CleanTalk

  • Hello,

    CleanTalk causes records in my DB slow log. I found, that Version: 6.41.1 has unoptimal /cleantalk-spam-protect/lib/Cleantalk/Common/Schema.php definitions.

    For example table sessions has defined ‘__indexes’ => ‘PRIMARY KEY (name(40), id(64))’ on two VARCHAR columns.

    The column “name” has in my installation only 2 values: ‘apbct_timestamp’, ‘apbct_urls’. None of these has length 40 characters. Both don’t need to be in column with charset utf8mb4, both much shorter ascii would work better. With caution the VARCHAR column type could be replaced with much faster ENUM.

    The column “id” is IMHO also useless utf8mb4 and should be replaced with ascii.

    The column “id” in my case has always length 64 characters, so VARCHAR should be replaced with CHAR.

    Mayby you might improve the performance by changing the PRIMARY KEY column order. Probably you could improve it even more by changing the table structure to contain separate columns for timestamp, urls instead of column “value” which value meaing is stored in column “name”.

    Could you please optimize your tables for faster websites?

    Thank you,

    Jan

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support dimitrycleantalk

    (@dimitrycleantalk)

    Hello @janmazanek,

    I’ve passed your details to the programmer staff.

    We will write back to you within 3 business days when we get any results.

    Please wait.

    Plugin Support katereji

    (@katereji)

    Hello.

    We looked at this and decided to implement your suggested changes. Thank you for bringing this to our attention.

    We will need a couple of months for it. We will inform you as soon as we have the results.

    Thread Starter jan.mazanek

    (@janmazanek)

    Hello @katereji, thank you for response and accepting the suggestion. I do understand, that there are probably many more changes to be done than I have highlighted. I hope it will need less than “couple of months”… We will see.

    Thank you for taking the performance into account.

    Plugin Support katereji

    (@katereji)

    Hello @janmazanek

    We will do our best. We will report the results in this thread.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.