15,000 records inserted into the database == 1 hour. Now, there are a couple of gotcha's here... The stored procedure being used to do inserts wasn't meant for batch inserting. All of the indexes were on, including a text context index on a CLOB field. Lets not forget about the triggers that are used to keep history. Just to ensure everything was inserted appropriately, I was using our Java classes that interface with the database, which also were not meant for batch inserts. Given all of that... I still don't think it should have taken 1 hour to insert 15,000 records.
So your next question is... Hardware? Well, it isn't running on a 486... The database isn't even on Intel, it is on a Sparc. Well... Sparcs can be slow too... But not 880's with 4GB of RAM and 2 CPU's.
At this pace, the batch should be finished by Sunday night at 9pm. That's if it doesn't die. I Just want to know how well it will perform on Monday morning when we try to do a search against that table... with its 750,000 extra rows :)
But... now that I think about it... I bet most of that time is spent connecting to the database over and over again.
Posted by carl at November 29, 2003 02:00 AM
Comments