Nope, normally there is no slow-down; I’ve double-checked many times. Of course, it’s always possible that there is a bug somewhere, so it would be best if you can get us that scene to support@chaosgroup.com so that we can check it out.
The below image was rendered in 3.4 and then in 3.3. Nothing was done to alter the scene between versions. The only thing I can think of that might cause this drastic of a slowdown, is that these models have UDIMs with 8k maps (tiledEXR) and V-RayDispMod. Other models in the same scene (without UDIM and Disp) render fine. Could UDIM and/or VRayDisp have a bug in 3.4?
The only thing that I can think of is that in V-Ray 3.40 we moved the texture cache value from the VRayHDRI texture to the renderer settings; if you modified the value in the VRayHDRI texture originally, make sure the same value is in the renderer settings.
If the issue is somewhere else, then I would need that scene too - looks like something that I should definitely take a look at. 3h seems like a horribly long time for such a simple render.
So for the first scene, Benchmark.zip, the difference seems to be because of a fix that was done to improve sampling when “clamp output” and “subpixel mapping” are both enabled - V-Ray 3.30 could produce horribly noisy results in some cases. This means that V-Ray 3.40 traces more rays, as can be seen in the VRaySampleRate render element, as well as the slightly reduced noise in some places.
If you disable “clamp output” and “subpixel mapping”, the render times between the two versions are very similar, with V-Ray 3.40 being marginally faster.