[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-910: --- Assignee: Evgheni Dereveanchin (was: infra) I think its duplicate of the 10-50 min task, feel free to close duplicate if its the case. > mock_runner.sh seems to run slower on newer slaves > -- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins >Reporter: Barak Korren >Assignee: Evgheni Dereveanchin > > After implementing speedup improvements for mock_runner.sh (Specifically > enabling it to deploy the chroot by extracting a tarball as opposed to > installing it with yum every time), I started monitoring run times for vdsm > check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to > initialize mock faster then ones running on new slaves (vm*) - 17seconds vs > 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on > /var/cache/mock -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
[
https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23926#comment-23926
]
Barak Korren commented on OVIRT-910:
the problem with logs is that you need to get then "hot" be cause they may
disappear fast...
Older slave log (fc24-vm15.phx.ovirt.org):
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5915/
{code}
...
12:01:51 Start: unpacking root cache
12:02:06 Finish: unpacking root cache
...
12:02:07 Init took 17 seconds
{code}
Newer slave log (vm0125.workers-phx.ovirt.org):
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5916/
{code}
...
12:04:19 Start: unpacking root cache
12:05:15 Finish: unpacking root cache
...
12:05:16 Init took 57 seconds
{code}
Then again, on (newer) vm0130.workers-phx.ovirt.org:
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5916/
{code}
...
12:02:45 Start: unpacking root cache
12:03:09 Finish: unpacking root cache
...
12:03:09 Init took 24 seconds
{code}
So not a 100% consistent result, still, we should find out how to get those 40
seconds back...
BTW I was sure the local disk was mounted on older slaves with noatime, looks
like that is not the case, maybe we should fix that...
> mock_runner.sh seems to run slower on newer slaves
> --
>
> Key: OVIRT-910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> After implementing speedup improvements for mock_runner.sh (Specifically
> enabling it to deploy the chroot by extracting a tarball as opposed to
> installing it with yum every time), I started monitoring run times for vdsm
> check_patch jobs.
> I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to
> initialize mock faster then ones running on new slaves (vm*) - 17seconds vs
> 57 seconds respectively.
> I suspect this may be because the older slaves have a different FS mounted on
> /var/cache/mock
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23920#comment-23920 ] Evgheni Dereveanchin commented on OVIRT-910: [~bkor...@redhat.com] some logs would be helpful :) Older slaves with local disk hook use ext4 on the secondary disk while newer ones write to rootfs which is XFS. I can try launching a dozen ext4 VMs so that we can compare performance. > mock_runner.sh seems to run slower on newer slaves > -- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins >Reporter: Barak Korren >Assignee: infra > > After implementing speedup improvements for mock_runner.sh (Specifically > enabling it to deploy the chroot by extracting a tarball as opposed to > installing it with yum every time), I started monitoring run times for vdsm > check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to > initialize mock faster then ones running on new slaves (vm*) - 17seconds vs > 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on > /var/cache/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-910: --- Description: After implementing speedup improvements for mock_runner.sh (Specifically enabling it to deploy the chroot by extracting a tarball as opposed to installing it with yum every time), I started monitoring run times for vdsm check_patch jobs. I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 seconds respectively. I suspect this may be because the older slaves have a different FS mounted on /var/cache/mock was: After implementing speedup improvements for mock_runner.sh (Specifically enabling it to deploy the chroot by extracting a tarball as opposed to installing it with yum every time), I started monitoring run times for vdsm check_patch jobs. I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 seconds respectively. I suspect this may be because the older slaves have a different FS mounted on /var/lib/mock > mock_runner.sh seems to run slower on newer slaves > -- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins >Reporter: Barak Korren >Assignee: infra > > After implementing speedup improvements for mock_runner.sh (Specifically > enabling it to deploy the chroot by extracting a tarball as opposed to > installing it with yum every time), I started monitoring run times for vdsm > check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to > initialize mock faster then ones running on new slaves (vm*) - 17seconds vs > 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on > /var/cache/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-910: --- Epic Link: OVIRT-400 > mock_runner.sh seems to run slower on newer slaves > -- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins >Reporter: Barak Korren >Assignee: infra > > After implementing speedup improvements for mock_runner.sh (Specifically > enabling it to deploy the chroot by extracting a tarball as opposed to > installing it with yum every time), I started monitoring run times for vdsm > check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to > initialize mock faster then ones running on new slaves (vm*) - 17seconds vs > 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on > /var/lib/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
Barak Korren created OVIRT-910: -- Summary: mock_runner.sh seems to run slower on newer slaves Key: OVIRT-910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra After implementing speedup improvements for mock_runner.sh (Specifically enabling it to deploy the chroot by extracting a tarball as opposed to installing it with yum every time), I started monitoring run times for vdsm check_patch jobs. I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 seconds respectively. I suspect this may be because the older slaves have a different FS mounted on /var/lib/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
