...never underestimate Samsung's lack of software optimization. I've had the Galaxy S6 for 11 months, and it's felt like I've taken a step back from when I had the HTC One M8, which is why I've decided to wait for the HTC 10 before deciding on a device.
I'm also sure of that as I have the same experience with Samsung flagships... However, since Samsung has improved its hardware and design since the S5 and the Note 3, I'd expect them to work a little harder on the software side of things. Maybe they need to hire more/better developers.
They have improved the S7. It's more consistent than the S6 ever was. Relative to itself, the S7 is a success and has stomped on performance problems decently.
My expectations are that for $800, I shouldn't experience slight framerate dips on 2D sidescrollers, I shouldn't experience hitches in Chrome and I shouldn't under-perform with loading pages compared to a $450 phone. Why are these compromises we're ok with on the android platform? So we can edit settings and change up the interface? The iPhone is slowly gaining the advantages Android has and the performance is out of this world on those phones. Samsung has put out something that is beautiful and powerful, but until it's on par with stock android phones when it comes to 60FPS performance, it's just never going to be something I drop almost a thousand bucks for. I'm all about speed and smoothness, and I think the performance to dollar value is still not there with the S7, but they are making progress.
And for those who wonder why I don't use an iPhone, it's because the interface is insanely boring and the phone is really boring to use. Google passed Apple in design with lollipop.
I have a hard time making comparisons to the iPhone because of the resolution differences. Samsung still has a ways to go with their software, but the consensus is always "Man I wish it was stock". I had both the 6P and 5X and neither of them are perfect in the performance department, either---especially the 5X. Now obviously there's a price difference, as you pointed out already, but there's so many other things that go into that price that make the Edge price worth it.
Slowly but surely, the S and Note lines are getting better software-wise, but I'm hoping next year it's their primary focus. They added back in the SD card, they brought back and improved the water resistance/dust resistance, and they found a way to increase battery size substantially without sacrificing too much on the design front. I think the last real complaint is Touchwiz and if that's what they're going to focus on this year, the S8 could be a phone that brings back a lot of people.
I have a 6P and my wife an S7.... It really didn't take too long to notice that there were some overall differences in how the phones each felt. The S7 is blazing quick, but it's also rough, surprisingly so... frame drops, stutters, weird little pops and wheezing that I don't see nearly as much as the 6P. Not saying that performance-wise, I never once see a burp or hiccup on the 6P, but they occur in far less frequency and severity as I see on the S7. Best way I can describe it is like having a really fast sports car that has some fuel mapping issues and misfires a little when you are putzing about town.
Now, it's hard to determine the whys here.... To get a good idea as to what Samsung is doing here, you'd have to be able to get into the kernel and play around. I have a suspicion that they are being really heavy on the race to idle... and try to avoid higher cpu states when at all possible and dropping down quicker than they really need... but it's moot since you need root access, system read/write access AND the ability to flash a custom kernel, all of which probably will never occur with the S7.
Well the difference is definitely in the software.
OP Is not crazy. 820 on Verizon here (S7 Edge), and can confirm all the behaviors indicated.
This phone (like every Samsung Galaxy I've ever used) has a buttery problem. That is, things are just not buttery smooth. In most cases, most people don't notice it. Either they aren't bothered by the microstutter or don't care about it. But for those of us who do care and are used to either iPhone devices or Nexus devices, it's particularly terrible.
Just to clarify - I noticed microstutter in Alto's adventure within the first 5 seconds. It is constant and persistent and I find it annoying in a way that doesn't seem quite rational (it's like a constant tick that won't stop). I'm comparing performance to an iPhone 6s Plus where it is flawless.
Additionally, I find that Chrome is and always has been a non-starter for smoothness on Galaxy phones and it hasn't changed with the S7 edge. I expected that. The gaming performance/lag bothers me immensely. It makes me think that Samsung has fundamentally altered the rendering software on the phone or has fundamentally altered the phones behavior in another way. With it's focus on power saving in games, I wonder if they haven't attempted to implement a truly dynamic clock speed scaling implementation that can't keep up with fast games. For example, in Altos Adventure, this would explain why slowdown occurs as soon as something even minorly intensive starts to happen.
That's all speculation however. All I can really say is that there is an issue with rendering on my phone (and OPs phone). Additionally, disabling the two Game Services as identified in the XDA Forums gaming performance thread did not solve the issue (although it did solve the automatic screen saturation issue).
In short OP: You aren't alone, there is a problem, I don't think most people can perceive the problem in it's "minor' forms, and I am only holding out hope that Samsung fixes the game rendering issue... I hold no such hope for Chrome.