I can not complain much about the current speed of painting (and sculpting) but i also did no comparisions.
However, i think that multithreading only gives max. 30% speed improvement. Its often more effective to find a bottleneck and optimize there or do some data caching.
this is not the case at all in my experience, and that of MANY others. In 3D Coat I am getting about 500%, yes, five hundred percent increases in the vox room on my 8 core system since Andrew FINALLY multithread a FEW of the necessary features many have been asking for. It's made the vox room usable for projects that were taking HOURS just to use simple tools like merge/pose/etc.
SECONDLY, have you ever used ZBrush with and without multithreading turned on? I EASILY get a 300-400% speed increase with multithreading turning on in the ZBrush prefs.
EDIT: just since no one else has posted since my last post, and not that anyone cares, but I wanted to also note that I get about 200-300% increase in photoshop with multithreading, and MASSIVE 700%+ increases in AFter effects(even for certain 3d operations). So a 30% increase with a multicore system, usually means either a process that isn't built for multithreading has been multithreaded, or the developer didn't care or know what they were doing to some degree. In some apps, multithreading isn't feasible(given the time investment to code it), but in 3D, MANY 3D apps, sculpting and otherwise, have proven that robust multithreading EASILY gives huge performance gains for many 3D operations, if the developer knows how to add them properly. Case in point, Andrew just proved this is too the case for 3D Coat with the recent vox room multithreading additions, so its a matter of will he do it, not can he do it, in my opinion.