When you are making systems that need to be very fast, every small bit helps. Some tips (thanks to Andrew) to fine tune performance:
- If you know that a value will not change in its lifetime, mark it as final (even those inside a method call). This will ensure that compiler accesses them faster. eg:
final int someValueToRefer;
public void aMethod(final Object obj, final int funcValToRefer){
final int aMethodValueThatWontChange = 1234;
} - Use message queues between systems you want to truly decouple. This makes sure that one part doesn't hold the other to ransom
- Use System.currentTimeMillis() if all you need is current time instead of new Date()
- Save dates in DB as long values instead of date objects
- When using a cache, save minimal information (saving a unique ID instead of the whole object, for example)
- Use connection pooling: for databases, thread pools, messaging queues
- Use synchronization blocks instead of full method synchronization
- When there is too much information to process, it may be desirable to first "group" similar chunks and process them in batches (for example, when you are sending stock alerts to you star trading team, you may want to group all the alerts by the time they are expected to go off)
- When there is a boolean to return, one can generally avoid creating one explicitly. eg:
boolean wasFound = false;
can be replaced by:
for(MyObject currObj:objectList){
if(currObj.getProperty().equals(valueLookingFor)){
wasFound=true;
break;
}
}
return wasFound;for(MyObject currObj:objectList){
if(currObj.getProperty().equals(valueLookingFor)){
return true;
}
}
return false; - Similarly, when we have a function that finds something and returns it, when you find it in a loop return right there instead of bothering to assign it to some var and break. eg:
MyObject retVal= null;
can be replaced by:
for(MyObject currObj:objectList){
if(currObj.getProperty().equals(valueLookingFor)){
retVal=currObj;
break;
}
}
return retVal;for(MyObject currObj:objectList){
if(currObj.getProperty().equals(valueLookingFor)){
return currObj;
}
}
return null;
No comments:
Post a Comment