On Windows, it uses HAXM to speed up Tizen application emulation, see https://developer.tizen.org/downloads/sdk/installing-sdk/hardware-accelerated-execution-manager.
Thanks, Ning -----Original Message----- From: general-boun...@lists.tizen.org [mailto:general-boun...@lists.tizen.org] On Behalf Of Carsten Haitzler Sent: Tuesday, April 09, 2013 3:55 PM To: Jeong-Joon Yoo Cc: general@lists.tizen.org Subject: Re: [Tizen General] Estimation of an execution time on Tizen emulator On Tue, 9 Apr 2013 15:57:36 +0900 Jeong-Joon Yoo <jeongjoon....@gmail.com> said: last i looked its actually an x86 qemu using kvm for acceleration if it can - on linux. on windows - no idea if it can accelerate execution. > Thank you Carsten Haitzler, > > So, the Tizen emulator does not emulate the arm core (shown in Tizen > reference), but it simulates only the Tizen platform on intel CPU, right? > > Best regards > > - JY > > On Tue, Apr 9, 2013 at 2:51 PM, Carsten Haitzler <ti...@rasterman.com> wrote: > > On Tue, 9 Apr 2013 14:35:25 +0900 Jeong-Joon Yoo > > <jeongjoon....@gmail.com> > > said: > > > >> Dear Tizen developer, > >> > >> Instead of measuring the execution time of an web application (or > >> native app) on Tizen reference phone, is it okay to measure the > >> execution time for the web application (or native app) on Tizen > >> emulator? > >> > >> In another word, in the following example, the value of > >> 'execution_time' on Tizen emulator is same with on Tizen reference > >> phone? > >> > >> begin_time = current_time_measure_function(); web_application > >> running; end_time = current_time_measure_function(); > >> > >> execution_time = end_time - begin_time; > >> > >> Is there another way to estimate the execution time of a web > >> application (or native application) with no use of the Tizen > >> reference phone? > >> > >> > >> Thank you in advance, > > > > none. every phone or tizen device will be different too based on hardware. > > tizen emulator simply runs as fast as it "can" on your pc - and that > > depends on your pc speed, how busy it is doing other things, > > drivers, kernels, scheduler, os etc. etc. > > > > only way to estimate is to get the exact hardware you want with the > > exact software, OR to create an EXACT clock-for-clock emulation of > > that hardware (including all I/O latency etc.) and frankly doing > > that kind of emulation is simply crazy - it's a huge amount of work, > > and then in 6 months u find that u no longer want to emulate THAT > > bit of hardware but a different one instead. > > > > the next "approximation" you can do is to run a series of benchmarks > > on the target hardware, then fiddle with your emulation environment > > to match them as closely as possible. e.g. forcibly clocking down > > your cpu if it's "too fast". using acpi throttling levels etc. this > > only can kind-of-approximate things. you still don't emulate I/O > > latency. this also assumes your pc is not "too slow" and can't keep > > up emulating to the same level as the target hardware... then your > > solution is "get a faster pc". :) > > > > > > -- > > Carsten Haitzler (The Rasterman) <ti...@rasterman.com> > -- Carsten Haitzler (The Rasterman) <ti...@rasterman.com> _______________________________________________ General mailing list General@lists.tizen.org https://lists.tizen.org/listinfo/general _______________________________________________ General mailing list General@lists.tizen.org https://lists.tizen.org/listinfo/general
