ACDK White Paper - Performance
Translation: Xue Changyu
The performance of the performance and development moment is usually contradictory
This chapter content:
Avoid synchronization
Container without synchronization
Use stack variables
General ACDK settings
Use dedicated dispensers R
Cancel Badcast and empty pointer detection
Use other garbage recycling
Use other object survival
Avoid synchronization
Container without synchronization
Use synchronization objects in the runtime time is expensive.
You may not need to use synchronization in some containers because the container can be used in a thread, using no synchronous container
* Do not use acdk :: util :: HashTable to use HashMap
* Don't use ACDK :: Util :: Vector to use ArrayList
Use stack variables
If an object instance is established in the stack, the synchronization of this object is not available. Because the object in the stack is the private object of each thread
See: stack. (Http://acdk.sourceforge.net/acdk/docs/hb/LANG/ACDK_HB_LANG_STACKVARS.HTML)
General ACDK settings
Use dedicated dispensers R
Cancel Badcast and empty pointer detection
Use other garbage recycling
Use other object survival
This article is the last article in which I translated the ACDK article. If there is time, I will try to translate foreign communication procedures. I am a programmer for communicating software, not a writer or translation, so if there is a translation issue, please forgive me: Xue Changyu 2004-12 Changning@ynmail.com
