You should really focus an general architecture of the app for optimizing...havn't looked into the provided example.
Your micro-optimizing suggestions for Java ...I think all Java guys are like ROFL now. Star visa Full Imports, String Concatenations in this example visa StringBuilder Really, if I carefully craft line numbers or embed no debug info in classes I can generate byte-identical class files with either import and string style. Import statements are not stored at all in Java class code and this string+string in one expression automatically use the StringBuilder pattern. you can lazy load classes - I just fear you mean something different ;) and it's the same problem like separating end points into micro apps - complex business code doesn't work that way - you have to load all that stuff anyway. Am Dienstag, 24. Juli 2012 09:00:15 UTC+2 schrieb Brandon Wirtz: > > I like that you use +'s to concat strings, it shows a real lack of > experience doing optimizations since that is the very first thing on every > list. > > > System.out.println(new Date() + ":" + new > Random().nextInt()); > > At least most of your code uses objects correctly I didn't find any > instances of places you did a type conversion functionally. That is > usually > one of the lowest hanging fruits, because it creates additional objects, > and > is a memory hog. > > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/iYnYrW5SL2EJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
