TL;DR, see [1] for the chart on the old page and new page.
By default the search uses the native autocompletion, which is usually what you want. E.g. if you search for "Barak Obama" you will see very few pageviews when most people actually wanted "Barack Obama". You can change this behaviour by going to the Settings > "Search method" > "Autocompletion including redirects". I still had trouble pulling it up with that setting though, something I'm not sure I can fix, as it seems to be an issue with the search API. In most cases however "Autocompletion including redirects" should reveal what you want, otherwise you could try "No autocompletion".
Anyway here's data for both the old location and new: [1]. There is some overlap because when you browse to a redirect, it will count as a pageview for the redirect itself, and not for the target article. If you want all pageviews, including redirects, consider using the "Redirect Views" tool: [2]
You probably are thinking to yourself that you always want redirects to be included, but doing so does not ensure completely accurate data. For instance, those redirects could have at some point in the past gone to a different article. So you'd then be getting (probably slightly) inaccurate numbers. There are talks of tackling this issue in the API itself, see [3]. In addition some pages have lots of redirects which could noticeably slow down the tool.
Another possible solution is to query the page move log. This is something I hope to actually do at some point, you can follow the ticket on Phabricator for updates [4]. This may be quite challenging, since there are some edge cases where the move log will steer you wrong and you end up querying the wrong pages.
Sorry for my excessive tech jargon, if it comes off that way :) Until we have a better way of handling this, first make sure you have the "Search method" set to "Autocomplete including redirects" or "No autocompletion", then simply type in the old page title.
Hope this helps,
~MA