Marc O.K. This is quite helpful. What I note most significantly here is you don't mention Reactor as a potential problem, which is my greatest fear. I thought that perhaps it was the overhead of the generic code that is causing the slow down. I seriously doubt it is my own code causing the problem because to do an update requires only generated code by Model Glue and Reactor. That is why I'm so concerned. If those were the source of the problem it would cause me to question whether we should use them. It seems apparent to me at this point that people using Reactor don't by nature experience slower inserts and updates.
As to my database I can tell you that each table has an auto increment primary key based on a sequence that is updated via a trigger when a record is created. At this point in development the largest table has perhaps 75 records in it. I will see what I can come up with when I go back to work on Monday. I can't simulate our Oracle database at home. Bryan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Marc > Sent: Saturday, March 03, 2007 4:25 PM > To: [email protected] > Subject: RE: [Reactor for CF] Any speed tips? > > Bryan, > > There are several ways to help yourself debug performance > issues; your first inclination of course is to look at the > code you've written and track your own tickCounts() at > strategic places to see which specific templates are running > slow... You might also consider grabbing yourself the 2-hour > limited version of SeeFusion. If nothing else, this will at > least confirm at the CF level that the problem you think you > are having is actually the problem. > > Beyond this, depending on what database you are using, you > might use some database-level tools to see what things look > like "from the rdbms's point of view". For example, if using > SQL Server, break out the Profiler and monitor the specific > transactions your database is receiving from your app. > > Come back to the list with some specific metrics you've > observed, and you'll probably get "better help, faster" than > if we have to just take pot-shots at each tier to figure out > where the performance problem is for you. > > You might also mention what indexes you've defined in your > database, an estimate as to the number of records in the > relevant tables, and check/review all the relevant CF > settings like "Save Class Files", "Trusted Cache", the > settings for your CF datasource, and the like. > > HTH, > > Marc > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Bryan S > > Sent: Saturday, March 03, 2007 1:37 PM > > To: [email protected] > > Subject: RE: [Reactor for CF] Any speed tips? > > > > Yes. I don't seem to be having a general performance > > issue. It's just inserts and updates that are a problem. > > > > Bryan > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of dickbob > > > Sent: Saturday, March 03, 2007 10:20 AM > > > To: [email protected] > > > Subject: Re: [Reactor for CF] Any speed tips? > > > > > > On debugging do you have "Report Execution Times" > turned off? > > > > > > dickbob > > > > > > > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > -- -- -- -- -- -- -- -- -- Reactor for ColdFusion > > Mailing List [email protected] Archives at: > > http://www.mail-archive.com/reactor%40doughughes.net/ > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
