[ 0016 ] fig1 illustrates a typical software stack for an embedded application and describes the hardware and software environment for the java environment . the java stack 100 includes an application layer 110 including applications and platforms . the application layer 110 interfaces with a java technology layer 120 . the java technology layer 120 includes a java application program interface 124 . applications developed for the embedded systems can use the java application program interface and java class libraries in the java platform . the java technology layer 120 interfaces with a real - time operating system 130 , which includes device drivers 134 . the real - time operating system layer 130 . as used in this description , the term operating system includes device drivers . the java application program interface 124 operates within the hardware context of the embedded system . in the example in which a display is being driven , a central feature is a data pipeline . the application program interface 124 provides an abstraction that allows the application programmer to remain unaware of the details of the underlying display hardware environment . [ 0017 ] fig2 is a block diagram of a client computer , or processor , 200 embodying a java virtual machine 210 . note that in this embodiment the java virtual machine is a software structure and embodied with the memory of the client computer 200 . within the computer 200 , computer hardware 220 is controlled by the operating system 230 . the java virtual machine 210 &# 39 ; s operations are implemented on the operating system 230 and computer hardware 220 . the java virtual machine 210 executes a program 250 loaded into the computer system 200 or otherwise accessed thereby . java programming normally comprises class files . a java interpreter 260 interprets java byte codes one by one . a just - in - time ( jit ) java compiler 270 produces native code to be run on the computer hardware 220 and provides compiled code in a compiled code register 280 . the compiled code register 280 provides object code for operations called by the java virtual machine 210 to the computer hardware 220 . the program 250 also comprises software to perform the method of fig3 below and command supplying of code to a compressor / decompressor 240 indicative of instructions identified by the operation of the method explained with respect to fig3 below . code representative of the most used software sections is compressed and stored in a code memory 290 . the code memory 290 comprises non - volatile ram . preferably the code supplied to the code memory 290 is compiled code . this compiled code is supplied for decompression via the compressor / decompressor to the compiled code register 280 on machine startup . since code memory 290 is expensive , compression will decrease memory requirements and reduce the price of many embodiments . it is desirable that the compression and decompression be lossless so that code is not corrupted . the means which may comprise particular elements of the compression and decompression processing are well - known in the art . varied means of compression and decompression without loss of data are available for this purpose . operation is described with respect to fig3 which is a flow diagram . operation begins at block 300 , at which time execution of the program 250 is initiated . since the memory 280 is volatile , compiling must begin each time operation is initiated . compiling is indicated at block 302 . at block 304 , the identity of a current code section is sensed . a code section is a particular line of code or java class that is compiled . at block 306 , a code section count is incremented for each section of code identified at block 304 . at block 308 , frequently used sections of compiled code are identified . “ frequently ” is defined by a pre - selected threshold count reached over a preselected time period . once frequently used code sections are identified , code indicative thereof is accessed . the accessed code is preferably compiled . the code is compressed at the compressor / decompressor 240 and written to the code memory 290 at block 312 , may be invoked from the memory 280 ( fig2 ). [ 0021 ] fig4 is an illustration of an abbreviated source code listing for an embedded program . for purposes of the present example , the embedded program is running an on - screen display . routines 410 are functions performed by the program 400 . different routines 410 can be selected based on knowledge of programming of the application which will be the most used functions of the program 400 . the particular ones of the routines 410 that are selected as the most typical functions invoked by users are called for purposes of the present description typical user scenarios 420 . [ 0022 ] fig5 is a flow diagram illustrating further operation and structure of the present invention . at block 500 , the program 400 is initiated . at block 502 , the first typical user scenario 420 is invoked . at block 504 , code sections that are utilized are identified . at block 504 , code is compiled . at block 506 , code sections invoked are identified . frequently used sections are saved at block 508 . at block 510 , a determination is made as to whether a user scenario 420 is complete . such determination is made by comparing the actual list of methods called in the user - invoked scenario to the total list of methods therein . if the user scenario is complete , then operation returns to block 502 to invoke a next user scenario , at the same time , a routine counter 512 is incremented . at block 514 , a determination is made as whether all user - invoked scenarios have been invoked and when they have , the program is stopped at block 516 . the invention does not require that all scenarios have to be converted to native code . in operation of fig5 in addition , at block 508 the compiled code is compressed saved to non - volatile memory 290 ( fig2 ). when the java virtual machine 210 ( fig2 ) is started again , it loads its on - screen display application 400 , which will constitute the program 250 in fig2 and will have available characterization information from the non - volatile ram 290 . the frequently used sections which are invoked in response to typical user scenarios 420 ( fig4 ) are decompressed and loaded immediately in the compiled java code register 280 . consequently the computer system 200 operates at full speed from the outset . the computer system 200 of fig2 also represents a delivered product in which characterization information is loaded into the non - volatile ram 290 prior to operation . consequently , a computer product is provided which will operate on the program 400 at full speed from beginning of its operation . the above disclosure will enable those skilled in the art to provide a method , machine - readable medium and apparatus constructed in accordance with the present invention even while making many departures from the specific teachings above .