Date: Tue, 16 Jun 2015 06:19:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 200447] Multiple time-related tests are having issues with Jenkins/Bhyve in the past few months; Jenkins/Bhyve on the cluster is non-performant/less deterministic compared to VMware Fusion 7 Message-ID: <bug-200447-32464-86CrRS7VU6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200447-32464@https.bugs.freebsd.org/bugzilla/> References: <bug-200447-32464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200447 --- Comment #5 from Garrett Cooper,425-314-3911 <ngie@FreeBSD.org> --- (In reply to Allan Jude from comment #4) We run into these issues all the time when our NFS stores go away for VMware ESXi hosted VMs at $work. That's why I was curious about how things are backed when running the Jenkins jobs. If things are truly hosted over NFS, that's horrible for performance (especially with NFS v4 when using TCP, which IIRC was the default); the test host needs to use a local disk -- preferably a RAID-1 SSD configuration using either graid or ZFS. The Jenkins job/infrastructure should not test out NFS latency/performance :)... -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200447-32464-86CrRS7VU6>