Re: Sun Solaris (SPARC processor) + Threads + performance/optimization

You are unlikely to see much improvement using threads (or processes), because the DB will almost certainly serialise all the DB activity. Especially if the inserts are all into the same table.

You'd be much quicker to use the bulk loader for your DB.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re: Sun Solaris (SPARC processor) + Threads + performance/optimization

Replies are listed 'Best First'.
Re^2: Sun Solaris (SPARC processor) + Threads + performance/optimization by gulden (Monk) on Apr 15, 2009 at 16:23 UTC
I've replaced the insert_into_db() by only making the `$indata->dequeue();` [download] And i'm getting no advantage in increasing the threads number and the CPU usage its about 10%!!! Something is wrong... I'm not taking advantage of parallelism/threads. Should I use more threads? more Thread::Queues? more Thread::Queues and passed them to different processing threads? Is there any problem with Perl and/or threads on Solaris? Should I use Forks instead of Threads?	[reply] [d/l]
Re^3: Sun Solaris (SPARC processor) + Threads + performance/optimization by BrowserUk (Patriarch) on Apr 15, 2009 at 20:02 UTC
Your process is IO-bound. Throwing more threads at it will not improve performance. Use a bulk loader. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]