On Wed, Apr 26, 2017 at 6:14 PM, Gianluca Cecchi <gianluca.cec...@gmail.com> wrote:
> On Wed, Apr 26, 2017 at 4:54 PM, Simone Tiraboschi <stira...@redhat.com> > wrote: > >> >> >> On Wed, Apr 26, 2017 at 4:52 PM, Gianluca Cecchi < >> gianluca.cec...@gmail.com> wrote: >> >>> On Wed, Apr 26, 2017 at 4:28 PM, Simone Tiraboschi <stira...@redhat.com> >>> wrote: >>> >>>> >>>> >>>> >>>> On 4.1.1, the 96% of the cpu time of ovirt-ha-agent is still spent in >>>> connect() in /usr/lib/python2.7/site-packages/vdsm/jsonrpcvdscli.py >>>> and the 95.98% is in Schema.__init__ in /usr/lib/python2.7/site-pac >>>> kages/vdsm/api/vdsmapi.py >>>> >>>> So it's still the parsing of the api yaml schema. >>>> On master we already merged a patch to reuse an existing connection if >>>> available and this should mitigate/resolve the issue: >>>> https://gerrit.ovirt.org/73757/ >>>> >>>> It's still not that clear why we are facing this kind of performance >>>> regression. >>>> >>>> >>> Does this mean that I could try to patch the >>> ovirt_hosted_engine_ha/lib/util.py file also in my 4.1.1 install and >>> verify if it solves...? >>> >> >> Unfortunately it's not enough by itself since it also requires >> https://gerrit.ovirt.org/#/c/58029/ >> >> >>> Or do I have to wait an official patched rpm? >>> >>> Gianluca >>> >> >> > And what if I change all the 3 files involved in the 2 gerrit entries: > ovirt_hosted_engine_ha/lib/util.py > lib/yajsonrpc/stomp.py > lib/yajsonrpc/stompreactor.py > > ? > > Yes, it should work although we never officially back-ported and tested it for 4.1.z.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users