search

at15 / hadoop-spark-perf

(Deprecated) Hadoop and Spark CPU performance Benchmark
MIT License
0 stars 0 forks source link

Virtualbox does not support perf counters #13

Closed at15 closed 7 years ago

at15 commented 7 years ago

https://github.com/mozilla/rr/wiki/Building-And-Installing

Based on the wiki, perf won't work in virtualbox environment, I don't know if I have time to let vagrant run with other provider that support this .... let me try what perf will have in virtualbox

saw it when googling for perf_event_paranoid https://github.com/mozilla/rr/issues/1616

Libvirt

at15 commented 7 years ago

it seems some are supported, but most are not, but it could be related with jvm, let me try it on my local machine ...

oops, it works on my local machine, hhhh

 Performance counter stats for process id '15651':

       1747.439062      task-clock (msec)         #    0.027 CPUs utilized          
            26,389      context-switches          #    0.015 M/sec                  
             1,543      cpu-migrations            #    0.883 K/sec                  
                24      page-faults               #    0.014 K/sec                  
     1,593,824,173      cycles                    #    0.912 GHz                    
       933,709,882      instructions              #    0.59  insn per cycle         
       181,063,042      branches                  #  103.616 M/sec                  
        12,540,255      branch-misses             #    6.93% of all branches        

      65.314086708 seconds time elapsed
at15 commented 7 years ago

failed on ubuntu when try to build the box using packer 

==> qemu: Creating hard drive...
==> qemu: Starting HTTP server on port 8337
==> qemu: Found port for communicator (SSH, WinRM, etc): 2640.
==> qemu: Looking for available port between 5900 and 6000 on 127.0.0.1
==> qemu: Starting VM, booting from CD-ROM
==> qemu: Error launching VM: Qemu failed to start. Please run with PACKER_LOG=1 to get more info.
==> qemu: Deleting output directory...
Build 'qemu' errored: Build was halted.

restart works, and it's amazing that they are using VNC to type in boot option, and it seems it would took a long time

and it seems I should use headless mode ... packer build -only qemu -var "headless=true" ubuntu-14.04.amd64.json

at15 commented 7 years ago

got error when vagrant up 

Call to virDomainCreateWithFlags failed: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
failed to initialize KVM: Device or resource busy
at15 commented 7 years ago

by default libvirt also does not support many counters, use the default box on fedora works ... but my ubuntu one won't work

^C./Ayi: Interrupt

 Performance counter stats for './Ayi web static':

          5.358546      task-clock (msec)         #    0.000 CPUs utilized          
                18      context-switches          #    0.003 M/sec                  
                 0      cpu-migrations            #    0.000 K/sec                  
               812      page-faults               #    0.152 M/sec                  
   <not supported>      cycles                                                      
   <not supported>      instructions                                                
   <not supported>      branches                                                    
   <not supported>      branch-misses                                               

      70.632247622 seconds time elapsed
at15 commented 7 years ago

now libvirt is running, besides, it seems libvirt use delta of base image, it would be better if the package functionality would work, good bye virtualbox \w/