[ZBXNEXT-4941] Investigate Oracle bulk update performance Created: 2019 Jan 07  Updated: 2024 Apr 10  Resolved: 2019 Mar 05

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: 3.0.24, 4.0.3, 4.2.0alpha2
Fix Version/s: 4.0.5rc1, 4.2.0beta1, 4.2 (plan)

Type: Change Request Priority: Minor
Reporter: Andris Zeila Assignee: Alex Kalimulin
Resolution: Fixed Votes: 1
Labels: oracle, performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File 4941-3_4_8.patch    
Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 48, Jan 2019, Sprint 49 (Feb 2019)
Story Points: 2

 Description   

Zabbix uses DBbegin_multiple_update(), DBexecute_overflowed_sql() and DBend_multiple_update() functions to compile multiple SQL queries into single query. On Oracle using separate queries might be better because of query caching.

Investigate performance difference on Oracle and if there are noticeable gains then change  DBexecute_overflowed_sql() to immediately execute the query instead of buffering it.

Also review code where DBexecute_overflowed_sql() function is used. It's quite possible that in some places it's used after buffering mutiple queries - then the code must be changed to call it after each assembled query.

 



 Comments   
Comment by Alex Kalimulin [ 2019 Feb 18 ]

Fixed in:

  • pre-4.0.5rc1 r89951
  • pre-4.2.0alpha4 r89968
Generated at Thu Apr 25 08:34:58 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.