rows per page option

[richlv]

revision 7207 comment said :
- [DEV-316] added rows per page field in user profile (Artem)

i don't see any effect of this option in rev 7218 - will actual implementation come later, or am i missing something ?

[Aly]

This functionality will be used later

[bashman]

What does this option (row per page) mean?.

[richlv]

if you open a list of elements (hosts, items, triggers etc) above that amount, they will be split in that many elements per page (and you will get paging controls at the top and bottom of each listing)

[bashman]

if you open a list of elements (hosts, items, triggers etc) above that amount, they will be split in that many elements per page (and you will get paging controls at the top and bottom of each listing)

Thanks richlv, so I could decrease the rows per page value in frontend in order to reduce io read in database and increase Zabbix performance.

I want to tune frontend because I notice a Zabbix Server low performance when there are 7 on line users simultaneously (Zabbix queue grows).

I have zabbix_server, apache frontend and mysql database in the same host.

I have done already mysql and apache tuning, so in frontend tune I'm resetting: Auto-logout, refresh and rows per page.

[richlv]

i don't think rows per page will help you a lot - by default it's 50, so the change wouldn't impact db load that much anyway.

to optimise frontend you could try enabling http compression, or maybe even making frontend read separate read-only replicated database - but that's a separate thread

[bashman]

Thanks richlv, I'll try http compression with lighttpd and mod_deflate.

What do you mean "making frontend read separate read-only replicated database"?.

[richlv]

What do you mean "making frontend read separate read-only replicated database"?.

have database replicated elsewhere, and frontend only access this replica. server would operate with its own copy of db and frontend load would not impact server in any way

[bashman]

Oh ok!, that sounds great. Thanks richlv.

[bashman]

Although if Zabbix admin operate new configuration through frontend, changes would only apply to frontend's DB copy, and zabbix_server's DB copy would not see changes.

[richlv]

Although if Zabbix admin operate new configuration through frontend, changes would only apply to frontend's DB copy, and zabbix_server's DB copy would not see changes.

sure - the read-only frontend would be used by users to look at things. for config, admin would use the "real" frontend

[bashman]

Ok thanks richlv. All the users can make Zabbix configuration changes or add new configuration, and you need another host to serve the new DB, so I discard this option.

But I'll have a look to http compression.