Your Development & Design Resource
Preview: Architecture: The Report Profile Article
02/22/2006 04:03 PM by Chris Toohey
I have a few articles in Draft status on this site, including a few on Domino online document management. With tomorrow being Show-and-Tell Thursday, I'll be publishing an architecture-themed article discussing the utilization of a profile document, data collection agent, and modified @dblookups to facilitate quick application performance on Domino databases with a high number of transactions. Here's a sneak peek:
While I feel it's important to provide real-time information to your application users, large databases that handle several thousand transactions per day, and more accurately, the reporting of or data interaction with said transactions can make even the most streamlined application slow with embarrassingly sluggish response times. In these cases, for those applications that exceed the "logical" document count for a Domino database (I'd say 200,000+ documents for a single database) I typically recommend the implementation of transaction profiles - the utilization of an architecture which I'll attempt to explain in the following article.
I've seen countless applications that tend to become sluggish just as it's finally being utilized to it's potential - and it's often the architecture reflecting the lack of understanding that while @dblookups and @dbcolumns are great for simple applications, they can prove disastrous for high-transaction databases.
While I don't consider myself a load-and-utilization expert, even I can see that there's going to be an issue with running an @dblookup on a view that contains 200,000 documents every time a form or document is opened simply to show the user the current document count or to return a subset of data from the database. It's for situations like this that I recommend the following...
Now, I mention that I consider a Domino database that has over 200,000 documents for a single database to fall into the category of "exceeding the logical document count for a Domino database". Anyone think that I'm off my rocker with this statement?
So new article coming out tomorrow, but a question for you today: what do you feel is the threshold for document storage in a Domino database before things start going awry?