Re: Informix and Oracle in the same shop

Richard Stanford wrote: > > On Wed, 4 Jun 1997, Tim Schaefer wrote: > > > Maybe this brings up an even broader question, that being, if > > the threading you affirm is in ODS, how come Oracle has not > > adopted a threading model of any consequence in their product? > > Actually, I'd have to say here that the current issue of multi-threading > is little more than a buzzword. For us, at least (<2gig processor-bound > heavy OLTP application) the fact remains that any one query of average > complexity will take up at most one CPU. Period. This is where most > apparent speed limitations are (in OLTP at least), rather than in the process > handling. > Well, not exactly. Multi threading an application may and can improve performance if the app is tightly coupled. But then again, it could hinder performance on an smp box. This will depend on how the OS handles threading. Just some food for thought. If you are running a multithreaded app on an smp box you run in to a problem when a child thread needs to access the shared memory of the parent task. I believe this is somewhat fixed by the OSs but it represents a problem of deadlock. I don't think that multi threading is going to be a detractor for an OLTP app. But it should help performance. Of course it all depends on the app. OLTP means Online Transaction Processing. But this could be anything from a simple POS app to a real time trading app. A point of sale app will just grab the information and slam it in to the database. (OK, there are some minor calcs and checks and balances.) The trading app may apply some mathematic calculation to valuate the cost of the asset or option. I think that you may get slightly better performance in a fork() call versus a thread. The other issue is that how will multi threading affect process migration? [While this is slightly skewed and off topic, it goes back to the idea that maybe multi threaded apps may not be the best paradigm.] -Mikey