Virtual Machine VM

VM acts as a hardware for performing operations. VM can be divided into two categories based on its working and functionality:
  • System Virtual Machine
  • Process Virtual Machiine
Based on its architecture VMs are divided into:
  • Stack based VM
  • Register based VM
System VM vs Process VM
The System VM simulates the complete system hardware stack and supports the execution of complete operating system. On the other hand, Process VM adds up layer over an operating system which is use to simulate the programming environment for the execution of the individual process.

 The Process VM is created when process begins and it ends when process gets terminated. The main purpose of process VM is to provide platform independency. JVM and CLR (Common Language Runtime) are examples of Process VM.

 Stack based vs Register based VM
A register VM is likely to have an intrinsic performance advantage over a stack based VM. Byte code verification is likely to be faster on a register VM because stack height integrity checks will be greatly simplified.

 As we know JVM is high performance and provides excellent memory management. But it need to be optimized for low-powered handheld devices. The Dalvik Virtual Machine is optimized for mobile devices. It is register based VM. It is optimized to use less space.

 Dalvik is the name of a town and Dalvik VM was written by Dan Bornstein. 

How DVM works
Every java program is compiled to byte code. The Java Byte code is then transformed into Dalvik byte-code with the help of dx tool and stored in .dex  file, and that's on what Dalvik performs operations such as verification and optimization.

In other words,
The javac tool compiles the java source file into class file. The dx tool takes all the class files of your application and generates a single .dex file.
The aapt (Android Assets Packaging Tool) handles the packaging process and combine .dex and manifest file and create .apk file that is your application.

Comments

Post a Comment

Popular posts from this blog

SQLiteDatabase (Without SqliteOpenHelper class)

Image
SQLite is a open-source relational database, that is used to perform database operations such as creating, storing, manipulating, retrieving and deleting data from the database. SQLitedatabase is used in android in two way: Using SQLiteOpenHelper class Without SQLiteOpenHelper class Here we are going to see the example of sqlitedatabase without SQLiteOpenHelper class. In this example, we will do following: Create a database Create a table Insert values into table Retrieve values Update values Delete values Create a database: SQLiteDatabase db=openOrCreateDatabase(DB_NAME, Context.MODE_PRIVATE, null); This opens a database defined in the constant DB_NAME, if it already exists. Else it creates a new database and open it. Create a table: db.execSQL("CREATE TABLE IF NOT EXISTS " + TABLE_NAME + " (ID INTEGER PRIMARY KEY AUTOINCREMENT, NAME TEXT, DESIGNATION TEXT, CONTACT NUMBER, AREA TEXT, CITY TEXT);"); This creates
Read more

Set current date to Button and Datepicker dialog

This tutorial is going to explain how to set current date on Button and when you click on that Button, DatePicker Dialog open to ask your new Date. When you set Date from datepicker dialog, selected Date will be set to that Button. A simple Layout with just only Button.   <Button         android:id="@+id/date"         android:layout_width="match_parent"         android:layout_height="wrap_content"         android:layout_marginTop="10dp"         android:onClick="setDate" /> For Date related task, you have to use Calendar class. And to get current Date, use method getInstance() of Calendar class. Calendar cal = Calendar.getInstance(); mYear = cal.get(Calendar.YEAR); mMonth = cal.get(Calendar.MONTH); mDay = cal.get(Calendar.DAY_OF_MONTH); mYear, mMonth, mDay is of int type. Now set date on Button: Button date = (Button) findViewById(R.id.date); date.setText( new StringBuilder().append( mDay ).append("/"
Read more

MVC Architecture in Android

Image
MVC represents Model-View-Controller Model : Manage the behavior and data of the application R esponds to requests for information about its state (usually from the view) Responds to instructions to change state (usually from the controller) Allows the views to produce updated output View : T ypically a user interface element O ne to one correspondence with a display surface Present the model to the user Generates the output representation to the user Controller : Controls both model and view Accepts input from the user and instructs the model and the view to perform actions based on that input Update view when model changes Update model when user manipulate the input
Read more