Re: Threading (Perl 5.8 ithreads) with Oracle 9i dumps core

Any special reason to use threads at all? They're still not 100% stable, so if you don't need them, you could just as well fork() your program and get a couple of seperate connections to do the work.

Using fork is probably more efficient too, if you're on some kind of Unix. You might even consider forks, which claims to be able to replace threads, though I've only played with it sofar, and not used it in any real application.

HTH,
Joost.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re: Threading (Perl 5.8 ithreads) with Oracle 9i dumps core

Replies are listed 'Best First'.
Re: Re: Threading (Perl 5.8 ithreads) with Oracle 9i dumps core by fx (Pilgrim) on Dec 19, 2003 at 21:15 UTC
The reason for using threads is that I have somewhere in the region of 30,000 updates to fire against a database and due to the database size, each update takes about 1 second. That's 500 minutes or 8 hours. That's far too long. In fact, I only really have a window of a couple of hours. I was hoping to fire off 10, 20 or 50 threads or something and just let them to the work. The other reason for threads is the ease at which I can share info (using queues). I will have a look at forks. Thanks.	[reply]

Replies are listed 'Best First'.

Re: Re: Threading (Perl 5.8 ithreads) with Oracle 9i dumps core
by fx (Pilgrim) on Dec 19, 2003 at 21:15 UTC

The reason for using threads is that I have somewhere in the region of 30,000 updates to fire against a database and due to the database size, each update takes about 1 second. That's 500 minutes or 8 hours. That's far too long. In fact, I only really have a window of a couple of hours. I was hoping to fire off 10, 20 or 50 threads or something and just let them to the work.

The other reason for threads is the ease at which I can share info (using queues).

I will have a look at forks.

Thanks.

[reply]