Bug 1508775

Summary:	Expose UploadImageChunkSizeKB in engine-config (used for ImageIO upload/download)
Product:	[oVirt] ovirt-engine	Reporter:	Yaniv Kaul <ykaul>
Component:	Backend.Core	Assignee:	Daniel Erez <derez>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	amureini, bugs, derez, ratamir
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:41:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2017-11-02 08:31:07 UTC

Description of problem:
Currently it is not exposed and we need to play with the DB directly to change it.
Changing it from the default 8192K to 819200K for example, improved performance (for me) from 20MBps to 60MBps. I think for the time being it's a configuration item we might need to enable tweaking.

Comment 1 Allon Mureinik 2017-11-05 12:21:18 UTC

Daniel, I see you already have a patch for this - can you please attach it here?
Thanks!

Comment 2 Daniel Erez 2017-11-05 15:29:38 UTC

(In reply to Allon Mureinik from comment #1)
> Daniel, I see you already have a patch for this - can you please attach it
> here?
> Thanks!

Sure, attached.

Comment 3 Avihai 2017-11-20 06:17:07 UTC

verified on ovirt-engine-4.2.0-0.0.master.20171118160347.git80b3e22.el7.centos.noarch

Comment 4 Sandro Bonazzola 2017-12-20 10:41:19 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.