Zabbix become slow after upgrade to 1.4.2

[ldil]

Hi there,

It did not solve the problem, but after putting back the original events.inc.php from the source the system runs better then when using the patch with the permission problems (http://www.zabbix.com/forum/showthread.php?t=7853)

Maby this helps.

Greetz Leo

[ldil]

Dear Alexei,

I have done some excessive testing about this problem, its for sure the events.inc.php is causing this problem with the high load. With the original events this problem is gone but everyone gets every event message.

Do you need some more information about the slow query log or any other input?

Greetz Leo

[kyi]

any new suggestions?

[themons]

I propose to be able to diasble the new permission system : "A group can access to a server group"

Personnaly i prefer the old one "A group cans access to a ressource (graph/screen)" I must be less hungry in sql queries

But its not a priority of zabbix developement.

[themons]

New Infos

I activate the mysql query loggin to see exactly what mysql is doing.
I made it on a test server which has a backup of a database and no zabbix server runnig.
I create a test screen which as no elements on it.

When I open it, then i look at the query log.
result:
36425 query logged
34965 query like : Select * from host where hostid=10xxx"

It may be a little bit havy no ????

[kyi]

jo, i ithing that this is the problem.
but what can we do? disable permissions or is it planned to rewrite the permission system?

[Alexei]

I activate the mysql query loggin to see exactly what mysql is doing.
I made it on a test server which has a backup of a database and no zabbix server runnig.
I create a test screen which as no elements on it.

When I open it, then i look at the query log.
result:
36425 query logged
34965 query like : Select * from host where hostid=10xxx"

It may be a little bit havy no ????

I absolutely agree. It seems that the current implementation of permission checks is, well, not efficient. We are going to fix this!

[themons]

Thanks Alexei to take a look at our problem

But

Will it be implemented in the next realese

[kyi]

thxs alexei, if it´s rewritten, i thing a switch to globally disable permissions will be nice.

[Alexei]

thxs alexei, if it´s rewritten, i thing a switch to globally disable permissions will be nice.

I won't change the existing permission schema. I'm going to fix this specific problem only.

The switch won't be implemented. Why?! Just make all your users Super Admins...

[eli.stair]

Web portal slowness, and ability to disable audit/perms...

Agreed Alexei, that disabling permission checks in general isn't "safe" or good practice. However in my case (and possibly many others) this would be exceedingly useful:

1) In my situation where I've got such a large number/frequency of hosts/items monitored that I have set up a read-only replicated slave of the database and interfaced it with a separate RO-database account and modified PHP fronend.

For this case I /HAVE/ granted the 'Guest' user account with admin privs, so that I can avoid having to login to view data from this portal (disables audit activity writes on every action), and also have unlimited access to browsing data without needing any login access. The PHP has been modified to set page defaults to items that do NOT generate large loop-queries over every host for perm checks... and I've disabled the login/configuration pages so that it's safe from spewing errors about not being able to update the database (remember, this is on a read-only mysql account) I'm using this for providing fast(er) access to support personnel, other users/applications, etc.


2) Unfortunately, the bigger problem than this is the inefficiency of the page creation/header scripts that generate multiple HUGE select queries for both permission checks AND generation of the items "available" to a selected user. As it is, with anything over 300 hosts (I'm running over 1000), each page load is delayed 1-20 seconds by all these "checks", that actually take longer than the choosing/generation of the data for display!

This needs to somehow be optimized, through better-formed queries, re-use of query results, more specialized-use tables not requiring such large scopes of scanning big tables with every host, using FK's for some permission tables to avoid having to search on EACH load... etc/, any/all of the above!




Cheers,

/eli

[Alexei]

I believe the performance issue has been fixed in the latest code.

[themons]

I believe the performance issue has been fixed in the latest code.

Alexei, are you talking about the SVN repository version ?

[Alexei]

Alexei, are you talking about the SVN repository version ?

Yes. Fee free to test it, I am very interested in any feedback since we are about to release 1.4.3.

[cbidwell]

Hi all, I'm still having issues with slow queries. I don't have a way to post images for you here, but my slow queries was, at one point, up to 2000+. I am currently using zabbix 1.4.4.Is there a way to streamline this so that there aren't any slow queries?