I did some initial testing of EIE into CMDB 2 and found it much slower (about 1/3 the speed). When you look at the logs and see all the processing it's doing to get the data mapped from the flat files then you can understand why!
However, by careful splitting of the data it is possible to use multiple parallel EIE data imports to speed things up. It is also possible to run multiple EIE daemons and direct the data at these to further improve performance. There is a white paper on EIE performance tuning. I guess it comes down to how many records, where they will go (CMDB is particularly slow), how much time you can allow and how complex you want the import to be. I doubt you'll get away without testing. Cheers Peter > We are strategizing a way to import a large number of records on a > routine basis. I'll just skip all the details since they really are not > relevant to the core question: > > Has anyone compared import speed between the EIE and using the "old > school" arimportcmd command line process in order to import a flat file? > I am just curious to see if there is a big advantage in speed either > way. There certainly advantages to both tools for doing this particular > data import but I have no idea how the speed compares and I don't have > the EIE installed on this server (and I'd rather not if I don't have > to). > > William Rentfrow, Principal Consultant > [EMAIL PROTECTED] > C 701-306-6157 > O 952-432-0227 > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
