Transparent concurrent atomic execution

1. A method of executing an application and associated application code on a virtual machine, including:

receiving an indication of a synchronized block indicating that a block of the application code should be atomically executed such that intermediate states that represent partial execution of the block of application code are not observable by other applications;

determining whether to speculatively execute the block of application code based at least in part on whether a lock associated with the block of application code has been previously contended, wherein the determination comprises:

in the event that the lock has not been previously contended:

executing the block of application code without speculation; and

in the event that the lock has been previously contended:

determining whether to speculatively execute the block of application code based at least in part on dynamic information associated with an object associated with a synchronized block; and executing the block of application code speculatively; and

attempting to execute the block of application code again upon failure of speculation;

wherein:

the application code does not indicate that the block of application code should be speculatively executed; and

the lock associated with the block of application code having been previously contended includes at least one attempt to acquire the lock during previous executions of the block of application code by a previous thread.

2. A method as recited in claim 1 , wherein the block of application code includes a programming language object method.

3. A method as recited in claim 1 , wherein the block of application code includes an object oriented programming language object method.

4. A method as recited in claim 1 , wherein the indication includes a Java synchronized method.

5. A method as recited in claim 1 , wherein the indication includes a Java synchronized block.

6. A method as recited in claim 1 , wherein the indication includes a .NET synchronized method.

7. A method as recited in claim 1 , wherein the indication includes a .NET SyncBlock.

8. A method as recited in claim 1 , further including committing stores made to a cache as a result of speculative execution.

9. A method as recited in claim 1 , further including aborting stores made to a cache as a result of speculative execution.

10. A method as recited in claim 1 , wherein the block of application code is executed on a Java virtual machine.

11. A method as recited in claim 1 , wherein the block of application code is executed on a .NET Common Language Runtime (CLR).

12. A method as recited in claim 1 , further including executing the block of application code by acquiring a lock upon failure of speculation.

13. A method as recited in claim 1 , wherein the block of application code may be executed speculatively when associated with a first object, and may be executed without speculation when associated with a second object.

14. A method as recited in claim 1 , further including: in the event that it is determined that the block of application code is to be executed without speculation, acquiring a lock.

15. A method as recited in claim 1 , wherein the application code comprises a subset of all code associated with the application.

16. A method as recited in claim 1 , wherein determining whether to speculatively execute includes determining whether speculatively executing the block of application code is advised based at least in part on dynamic information associated with an object associated with a Java synchronized block.

17. A method as recited in claim 1 , wherein determining whether to speculatively execute includes determining whether speculatively executing the block of application code is advised based at least in part on dynamic information associated with an object associated with a .NET SyncBlock.

18. A system for executing an application and associated application code on a virtual machine, including:

a processor configured to:

receive an indication of a synchronized block indicating that a block of the application code should be atomically executed such that intermediate states that represent partial execution of the block of application code are not observable by other applications;

determine whether to speculatively execute the block of application code based at least in part on whether a lock associated with the block of application code has been previously contended, wherein the determination comprises:

in the event that the lock has not been previously contended:

execute the block of application code without speculation; and

in the event that the lock has been previously contended:

determine whether to speculatively execute the block of application code based at least in part on dynamic information associated with an object associated with a synchronized block; and execute the block of application code speculatively; and

attempt to execute the block of application code again upon failure of speculation;

wherein:

the application code does not indicate that the block of application code should be speculatively executed; and

the lock associated with the block of application code having been previously contended includes at least one attempt to acquire the lock during previous executions of the block of application code by a previous thread; and

a memory coupled with the processor, wherein the memory provides the processor with instructions.

19. A system as recited in claim 18 , wherein the indication includes a Java synchronized method.

20. A system as recited in claim 18 , wherein the block of application code includes a programming language object method.

21. A computer program product for executing an application and associated application code on a virtual machine, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:

receiving an indication of a synchronized block indicating that a block of the application code should be atomically executed such that intermediate states that represent partial execution of the block of application code are not observable by the application other applications;

determining whether to speculatively execute the block of application code based at least in part on whether a lock associated with the block of application code has been previously contended, wherein the determination comprises:

in the event that the lock has not been previously contended:

executing the block of application code without speculation; and

in the event that the lock has been previously contended:

determining whether to speculatively execute the block of application code based at least in part on dynamic information associated with an object associated with a synchronized block; and

executing the block of application code speculatively; and

attempting to execute the block of application code again upon failure of speculation;

wherein:

the application code does not indicate that the block of application code should be speculatively executed; and

the lock associated with the block of application code having been previously contended includes at least one attempt to acquire the lock during previous executions of the block of application code by a previous thread.

22. A computer program product as recited in claim 21 , wherein the indication includes a Java synchronized method.

23. A computer program product as recited in claim 21 , wherein the block of application code includes a programming language object method.