I have such experience. If you understand what you want and how to create table that will be very fast all will be ok. But If you never done something like this as the result you may create more slowly multithreading application. For today I have one application that without any problem in the same time writing data to one table from 300 threads(2 Core, 2GB RAM and small part of RAID5). You need RAID10 from HDD or SSD and fast processor, but no one hardware could compensate errors of architecture.

When you start a lot of instances of one application - it's like multi-threading, it is slower than one inctance? )

If you want use multiple thread you must to try do it, than analyze errors and do it again, until results became good )

 

Hi,

do you have any experience in selecting from / inserting to table from multiple threads? Is it faster in comparision to one thread which selects / inserts data in queue?

What is your opinion on this? My gut tells me that it will be always slower in comparision to single thread. But maybe I am wrong and it is worth the hassle to use separate threads?

Assumption here is that each thread pulls of data with different primary / secondary keys and also inserts with different keys.

I would like to hear your opinion about this topic.

Thanks you.

-- 
Regards,
Markov Dmitri