Quote:
it worked it was (much) slower than just executing BigInt.Multiply on one thread
Yes, that's what I do expect for such a case. When you do the operation in different cores, several values need to be checked and updated for each step of the operation between the individual cores, and that slows the process down severely. By doing multi-threading the wrong way, an application can be slowed down extremely.
There are some articles here on CP explaining the background in great detail.