This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I inherited an application which opens to the public every february. During this february I was having up to 300 concurrent users acessing in less than a minute. I used up 60% of the cpu on a shared server and database connectivity was slooooooowwwwwwwww,aside from increasing the connection pool I would like to visit the database less often. Instead of going to a tablewith a list of city names and their code number I want to save this information into a java singleton object (the application goes down everyday at midnight for 10min while the information in the databse is extracted elsewhere so the singleton will be refreshed everyday and the list of cities hasnt been modified for years). Would I see a peformance benefit if I save this information in memory? (It is queried everytime a user logs in).