[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

Tuesday, 30 January 2018

This is a multi-part message in MIME format...

------------=_1517298465-14824-170
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

     [
https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir...
]

Daniel Belenky updated OVIRT-1866:
----------------------------------
    Epic Link: OVIRT-400

...
 Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY
 ----------------------------------------------------------------

                 Key: OVIRT-1866
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866
             Project: oVirt - virtualization made easy
          Issue Type: Improvement
            Reporter: Daniel Belenky
            Assignee: infra

 It seems that pipelines now have support to configure their behavior of serialization of
objects, and since we know that this serialization never worked for us as we'd expect
it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid
serializing and maybe boost the performance.
 [Link to subject in jenkincci-dev
google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51...]

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100077)

------------=_1517298465-14824-170
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jir...
]</pre>
<h3>Daniel Belenky updated OVIRT-1866:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Use PERFORMANCE_OPTIMIZED pipelines instead of
MAX_SURVIVABILITY</h3>
<pre>     Key: OVIRT-1866
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
Reporter: Daniel Belenky
Assignee: infra</pre>
<p>It seems that pipelines now have support to configure their behavior of
serialization of objects, and since we know that this serialization never worked for us as
we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which
will avoid serializing and maybe boost the performance. [Link to subject in jenkincci-dev
google|<a
href="https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32...
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100077)</p>

------------=_1517298465-14824-170--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011