Download & Extend

performance::this module adds 10 times nearly queries to the database!!!

Project:Localization client
Version:6.x-1.7
Component:Miscellaneous
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

before using this module::
Executed 90 queries in 157.45 milliseconds. Queries taking longer than 5 ms and queries executed more than once, are highlighted. Page execution time was 489.2 ms.
after using this module::
Executed 539 queries in 343.79 milliseconds. Queries taking longer than 5 ms and queries executed more than once, are highlighted. Page execution time was 934.44 ms.

this is just the result by using cacherouter , if not using , may be worse

is there a way to just allow one user to using this module and the other could not , thus , the mysql will not be overload to the annoymous

Comments

#1

This should only ever happen to admin users, and is intended. Otherwise there would be no way to get the exact list of strings used for the page. If you can reproduce it slows down anonymous, then that is a bug. If it slows down admin this way, then it is intended. We have no way to identify which part of the big cache blob was used and many long strings are not in the cache blob even to display the interface properly.

#2

Also, not sure in what math 539 equals 10 times 90.

#3

actually , i don't want the first user (userID=1) to use this module ,
because i always use this user to do some hight-athority job

#4

Right. Admin users usually don't care for the amount of queries that happen for them.
Still l10n_client is a tool that might be present for a certain time on a server for several translation users.
If we might be able to temporarily inactivate the l10n_client for a certain user (user account settings) this would be great.

In inactive case for current user we then can stop disabling the locale cache in hook_init.

Finally we'll have this tool available for a longer time without huge impact in performance.

#5

Status:active» fixed

We've added user capabilities to disable the plugin.
Also overhead currently only is added if user has permissions for this module.

#774794: enable/disable l10n_client based on user settings

So you're able to enable the module and still users can controle if they're ready for the overhead. And the approach of l10n_client implementation simply needs this overhead to work.

#6

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.