I've found that partitioning doesn't do much in the area of performance except to usually make it slower even if your code is written well enough to take advantage of so called partition elimination. A monolithic table with the correct indexes and the correct code playing against it will usually beat the identical index/code combination on a partitioned table. I say "usually" a bit tongue in cheek because I've not yet seen a partitioned table beat a monolithic table for performance.
My disclaimer there is that I have seen some people claim that partitioning helped performance but, for those I'm aware of, it was the indexing they had to do to partition the tables that really made the difference. Doing similar indexing on their old monolithic table was still faster. Fixing bad code is even better.
Partitioning <> Performance. What partitioning is really good for is index maintenance, backups, and the ability to do "Piece Meal" restores if the need should ever arise.