Unless the JPMath.Triangle constructor takes a significant amount of time, then it's likely that parallelisation will slow down processing rather than accelerate it. As I said yesterday to a different user (or a sock puppet account)
Improve the speed of for loops[
^] parallelisation is not a magic bullet and it needs to be carefully thought about, or it can slow you down rather than speed you up.
When you parallelise code, you add threads - and there is a processing cost associated with each thread you create because each thread needs it's own stack space and "control block" so the system knows what state it is in, what priority it has, who owns it, and so forth. There is also a shutdown cost, though that is smaller - releasing memory and other resources back to the system. Those costs aren't trivial and if the setup / shutdown time exceeds the processing time each thread uses then your app will run slower.
Additionally, thread execution is restricted by the hardware it runs in: if you have 4 cores then the whole system can only execute 4 threads simultaneously - all the others are "frozen" waiting for core time. And there is a cost associated with freezing and unfreezing a thread as well: nothing is for free! If you have 8 cores, then it's 8 threads and so on.
So if you add many threads by parallelising indiscriminately, you very quickly run into the law of diminishing returns: your app slows down because you tried to speed it up!
I'd start by first measuring the current speed really carefully over a range of data sizes so you have a benchmark to work from, then looking at how you could parallelize the outer loop only, so that each iteration of i is on a separate thread but j and k remain very much the same: you will need to pass each thread a different value of c instead of using a simple increment in the innermost loop. That might speed things up, it might not. I suspect that if your triangle constructor is trivial you aren't going to get a major speed increase in any way.
Parallelism isn't a magic bullet - I know I said that above but it bears repeating - you need to think about it very carefully and it will change and complicate your code so it'll be a lot harder to test, debug, and maintain.