|Post date: 2007-05-27 12:10|
Yes, it depends on the need for performance/time you can spend developing.
But if you go with the profile solution it must be possible to do save(false,false) and have a scheduled agent readjusting the numbers every night in case there was an update that was missed. I do something similar in this forum for the post counts and last updaters.
Is the solution a heavy traffic database? The servlet solution, although fun to develop, seem a little overkill?
But if you go with the servlet you could have a separate thread that read up the coll.count every 5-30 minutes and save the result in memory for fast delivery when the servlet is called.
Servlets that do no disk access respond so fast that you can not measure the execution time using the internal Java timer.